IRC log for #maemo-ssu on 20130507

02:10.16*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@14.151.29.219)
02:28.30*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:04.06*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
03:22.26*** join/#maemo-ssu M13 (~Miranda@83.149.34.197)
04:25.22*** join/#maemo-ssu _rd (~rd@p57B4B639.dip0.t-ipconnect.de)
05:17.11*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
06:12.16*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz)
06:41.51*** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn)
06:57.41*** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-227.residential.rdsnet.ro)
07:34.54*** join/#maemo-ssu andre__ (~andre@ip-62-24-76-119.net.upcbroadband.cz)
07:34.54*** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper)
07:40.52*** join/#maemo-ssu sunny_s_ (~sunny_s@86.57.254.135)
07:47.33*** join/#maemo-ssu M13 (~Miranda@83.149.35.212)
08:04.01*** join/#maemo-ssu futpib (~futpib@89.106.197.102)
08:06.51*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:10.30*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:16.42*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:22.56*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:26.02*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:28.51*** join/#maemo-ssu wmarone__ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:34.34*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:39.46*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
08:40.36*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:42.43*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
08:52.32*** join/#maemo-ssu wmarone__ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
09:01.15*** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz)
09:50.58*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
10:12.57*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
10:15.36*** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz)
10:23.43*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-wvytgaypdpomyepi)
11:31.11*** join/#maemo-ssu mnzaki (~mnzaki@41.46.178.191)
11:55.51*** join/#maemo-ssu macmaN (~chezburge@138.167.190.90.dyn.estpak.ee)
11:59.50*** join/#maemo-ssu tg (~irc@eu.tgbit.net)
12:13.11*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
12:45.47*** join/#maemo-ssu AndrewX192 (~andrew@131.191.116.183)
12:45.47*** join/#maemo-ssu AndrewX192 (~andrew@unaffiliated/andrewx192)
12:46.15*** join/#maemo-ssu tg (~irc@eu.tgbit.net)
12:48.32*** join/#maemo-ssu arcean (~Tomek@apn-46-76-189-169.dynamic.gprs.plus.pl)
12:50.27Palimerlin1991: ping
13:54.50*** join/#maemo-ssu NIN101 (~NIN@p57B9E147.dip0.t-ipconnect.de)
14:00.54Palithis merge request https://gitorious.org/community-ssu/modest/merge_requests/13 for modest is there quite a long
14:01.08PaliI'm going to merge it into master (cssu-devel)
14:54.48merlin1991Pali: yeah, go ahead
14:54.59merlin1991I hope I'll finally get to work on the -t release today/tomorrow
14:55.17Palimerged and pushed to cssu-devel
14:55.38kerioyay :D
14:56.31merlin1991currently updating servers from squeeze to wheezy
14:56.41merlin1991I kinda fear touching merlin1991.at though
14:56.49kerionay D:
15:01.37merlin1991blindly running dist-upgrade is a scare thing without proper backups :D
15:01.46merlin1991s/scare/scary/
15:39.46*** join/#maemo-ssu asem (~chatzilla@197.150.168.252)
15:59.42merlin1991makes backups
16:25.25keriobackups are good!
16:40.39Paliand sometimes you find that you have backup in backup in backup in backup...
16:40.55Paliand trying to find out why you have full HDD :D
16:41.26kerioi solve the backup problem by not having anything important
16:59.34*** join/#maemo-ssu Sicelo (Sicelo@gets.high.on.ircspeed.net)
17:14.21*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
17:25.54*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz)
17:33.10*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
18:08.12Paliit looks like my change to rcS-late working fine. it detecting maemo installed on SD card and eMMC and also correct filesystems
18:08.32Paliand has support for static /etc/fstab
18:38.57*** join/#maemo-ssu M4rtinK (~M4rtinK@46.227.13.46)
18:43.07kerioPali: does it still break horribly if you use LABEL= or UUID=?
18:44.44Paliah, I forgot this
18:45.31kerioand are you still using your crappy version of fsck fs type autodetect?
18:47.02Paliyes and it is not crappy
18:47.24kerioadds completely unnecessary complexity
18:47.26PaliI really do not want to call ext fsck untility on fat/ntfs partittion
18:47.48kerioit won't do anything except complain that it can't find any superblock
18:47.59kerioactually, hold on
18:48.03kerioYOUR version will do that
18:48.10Palikerio, can you write your fstab with label or uuid?
18:48.17keriomy fstab uses LABEL
18:48.23keriooh you mean pastebin it somewhere?
18:48.26Paliyes
18:48.39*** join/#maemo-ssu ruskie (ruskie@sourcemage/mage/ruskie)
18:48.45kerioPali: it's *your* version that will blindly call fsck.$type_in_fstab
18:48.47Paliblkid will transtale it to /dev/device
18:48.48keriofsck will use blkid
18:50.17keriono, seriously, are you really trying to do this to avoid calling e2fsck with a "wrong" argv[0] that WON'T BE USED AT ALL BY IT?
18:51.22kerioPali: http://fpaste.org/10910/67952673/
18:51.52Palikerio, ok I can change code which will call generic "fsck" version
18:52.31Palibut what happen if: you have ext4 in fstab and partition is extš?
18:52.37Paliext3?
18:53.14Palistrace told me that generic fsck using data from /etc/fstab
18:53.45Paliso this *can* damage/convert filesystem
18:53.53kerio`fsck LABEL=lolol` correctly picked up my vfat partition
18:54.02kerioand that's nowhere in fstab
18:54.57kerioand regardless
18:55.39keriodosfsck just said "logical sector size is zero" on my ext4 partition
18:55.55kerioand e2fsck complained about "The superblock could not be read or does not describe a correct ext2
18:55.56keriofilesystem.  If the device is valid and it really contains an ext2
18:55.56keriofilesystem (and not swap or ufs or something else), then the superblock
18:55.56keriois corrupt"
18:56.02kerioand did nothing
18:56.15Paliare you called it with -p or -y?
18:56.18*** join/#maemo-ssu _rd (~rd@p57B4B639.dip0.t-ipconnect.de)
18:56.32kerioif a fsck tool can't figure out if what's ahead of it /is/ a file system of the correct type, what the hell can it do?
18:56.53kerioPali: yep
18:57.16Palifilesystem detection is overwritten by /etc/fstab
18:57.25kerioso that's even better
18:57.35Palibut we using HAL/blkid for detection
18:58.02keriowe're also using blkid to make fstab
18:58.05Paliso if you specify BAD filesytem in fstab for SD card, then it still works
18:58.18Palinow you can have static fstab
18:58.30kerioand at that point, it becomes your responsibility
19:00.58DocScrutinizer05wtf are you doing?
19:01.23Paliok, I will extract only device line from /etc/fstab for /home and call generic version fo fsck on it
19:01.39kerioPali: omg omg omg omg wait
19:01.40keriofsck /home
19:01.51kerioi just tested it, it works
19:02.18Pali$ fsck /home
19:02.22Palithis not working
19:02.30Palifsck.ext2: Is a directory while trying to open /home/
19:02.36keriowut
19:02.50keriono, /home
19:02.58Palifsck /home called fsck.ext2
19:03.09Paliwhy?? I have ext3 on /home
19:03.37keriouser@kerio900:~$ sudo fsck -n /home
19:03.37keriofsck 1.41.3.maemo0 (12-Oct-2008)
19:03.37kerioe2fsck 1.41.3.maemo0 (12-Oct-2008)
19:03.37kerioWarning!  /dev/mmcblk0p2 is mounted.
19:03.37kerioWarning: skipping journal recovery because doing a read-only filesystem check.
19:03.38kerioN900_optfs: clean, 35771/643376 files, 257958/2572288 blocks
19:03.56Paliok, it looks like if filesystem is unknown it calling fsck.ext2
19:04.03kerioseems so
19:04.17kerioand stop calling it fsck.ext2 like it's something different from fsck.ext3 or e2fsck
19:04.30keriodoes it work on your end without the trailing slash?
19:04.54Palihttp://pastebin.com/xaDjhU9R
19:05.08kerioyeah, yeah, i got that too
19:05.20keriothe mountpoint is "/home", though
19:05.21kerionot /home/
19:05.45Paliyes, working now: http://pastebin.com/PpthS5mE
19:06.00Palidetected as ext3
19:06.01Paliok
19:06.47kerioDocScrutinizer05: i'm trying to turn a 'fsck.`grep /home /etc/fstab | cut -d" " -f3` `grep /home /etc/fstab | cut -d" " -f2' into a 'fsck /home' in your future... rcS-late? preinit? where is this?
19:07.01Palikerio, ok, then I only call "fsck -p /home"
19:07.02keriorcS-late
19:07.05PalircS-late
19:07.11kerioPali: use -a, -p isn't standard
19:07.15kerioit's the same for e2fsck, though
19:07.47kerio...and if we assume that /home must be on extfs, or something whose fsck supports -p, we can just use -p i guess
19:07.51Palifor vfat too?
19:07.59DocScrutinizer05> >For  most types all the mount program has to do is issue a simple mount(2) system call, and no detailed knowledge of the filesystem type is required.  For a few types how-              ever (like nfs, nfs4, cifs, smbfs, ncpfs) ad hoc code is necessary. The nfs, nfs4, cifs, smbfs, and ncpfs filesystems have a separate mount program. In order  to  make  it              possible  to  treat all types in a uniform way, mount will
19:08.01DocScrutinizer05execute the program /sbin/mount.TYPE (if that exists) when called with type TYPE.  Since various versions of the              smbmount program have different calling conventions, /sbin/mount.smbfs may have to be a shell script that sets up the desired call.<<
19:08.29kerioPali: dosfsck doesn't have a -p option i think
19:08.35Palihahahaha, we have messybox version of mount
19:08.45Paliand there autodetection not working properly :D
19:08.47keriooh nvm, it still understands -p
19:09.09kerioi think that -a and -p are completely synonymous
19:09.21DocScrutinizer05> >If no -t option is given, or if the auto type is specified, mount will try to guess the desired type.  Mount uses the blkid library for guessing the  filesystem  type;  if              that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems.  All of the filesystem              types listed there will be tried, except for those that are
19:09.22DocScrutinizer05labeled "nodev" (e.g., devpts, proc and nfs).  If /etc/filesystems ends in a line with a single *  only,  mount              will read /proc/filesystems afterwards.<<
19:10.07kerioDocScrutinizer05: fsck, not mount
19:10.23PaliDocScrutinizer05: this is not tru for our stupid version of mount provided by busybox
19:10.23DocScrutinizer05who the fuck cares about fsck?
19:10.35keriohas strong opinions regarding fsck
19:10.45Paliit really cannot detect ext4 filesystem
19:10.46keriothe new rcS-late will support automatic preening on boot
19:10.58kerioPali: e2fsck is a single binary ;_;
19:11.37kerioext4 doesn't even exist as a concept, in e2fsprogs, it's just a set of default options to mke2fs
19:11.55DocScrutinizer05fsck can't detect *anything* since you're *usually* dealing with a _broken_ fs when it comes to fsck, and a broken fs is impossible to reliably detect it's type
19:12.18kerioDocScrutinizer05: if you can't detect its type, then it's too borked to fix already
19:12.26keriooften, it's only slightly borked
19:12.27DocScrutinizer05BS
19:12.38keriomissing extfs superblock?
19:12.49keriolike, missing extfs superblock and missing all the superblock backups
19:12.59DocScrutinizer05pff, so one single block got overwritten?
19:13.15keriovarious blocks
19:13.27DocScrutinizer05you can not reliably detect a broken fs' type
19:13.32kerionot reliably
19:13.48DocScrutinizer05that's a basic truth
19:13.53keriobut if the broken fs is not too broken to be unfixable, you can often detect it
19:14.03kerioand regardless, fsck uses /etc/fstab data too
19:14.07DocScrutinizer05that's also why fsck never gets executed automatically in fix-all mode
19:14.09PaliDocScrutinizer05: now we tested that generic fsck using /etc/fstab and blkid for detecting filesytem
19:14.32Paliand my scripts used fstab/blkid too
19:14.52Paliso there is really no need to use long scripts for that...
19:15.23keriotrusts Pali, but trusts the e2fsprogs authors more
19:15.36DocScrutinizer05shakes head on what it might be you guys try to do here, and wanders off
19:15.43kerioare they also the kernel guys?
19:16.29kerioDocScrutinizer05: more configurability in rcS-late regarding the mounting of /home and the generation of fstab
19:16.49kerioincluding (Pali: optional?) automatic preening
19:16.59DocScrutinizer05so wtf has fsck to do with that??
19:17.13kerioaka fsck in "do a summary check and only fix broken stuff if you're certain you can fix it" mode
19:17.17Palioptionaly call fsck before mounting
19:17.33Paliext* filesystems need to be checked every N mounts
19:17.54DocScrutinizer05ooh you are sure about thatß
19:17.59DocScrutinizer05?
19:18.10kerioalways uses -C 0 -i 0 when mke2fsing
19:18.15Paliand in nokia original rcS-late was check: if mounting /home failed then try to run fsck
19:18.41PaliDocScrutinizer05: this is default behaviour of mkfs.ext3
19:18.49Palido you think that is incorrect?
19:18.57keriomkfs.ext4 -C -1 -i 0 /dev/mmcblk0p1 #YOLO
19:19.22DocScrutinizer05yes, and it was rather idiotic since it didn't inform user, not to mention any sane thing like opening console to show diagnostic output and even ask for user interaction to fsck
19:19.27Paliwhy every desktop linux distribution using that default behaviour too when installing
19:20.48kerioDocScrutinizer05: my laziness regarding the preparation or the acquisition of food is winning over my hunger, i think i'm going to follow your diet method this evening
19:22.09*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
19:56.02*** join/#maemo-ssu _rd (~rd@p57B4B639.dip0.t-ipconnect.de)
20:03.06*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
20:28.45Palikerio, now when I enabled auto fsck on my /home (n900) it show me very bad message
20:28.56Palifilesystem is corrupted
20:28.58kerio:c
20:29.08keriois it corrupted?
20:29.23PaliI backed up (via dd) full partition to pc (via usb)
20:29.37Paliand started calling fsck -y on home device
20:29.48Palifsck wrote a lot of lot of errors
20:29.53Paliand *crashed*
20:29.58kerioneat
20:30.07Paliand now fsck crashing always
20:30.35Palibut (before calling fsck) partition is/was mountable and maemo worked
20:30.50keriobtw, we should upgrade e2fsprogs
20:31.09Palinot going to extract data from backup on pc and I will call mkfs.ext3 on /home
20:31.25kerioPali: again, you keep saying "mkfs.ext3" as if to say that it changes things
20:31.56PaliI will create clean fileystem
20:32.03kerioPali: call mkfs.ext2 on it, too
20:32.05Paliand then copy files extracted from dump
20:32.19Paliseems there is no way to normal recovery
20:32.32kerioyou could just copy the files from the backup you made before tinkering with filesystems
20:32.56kerio:>
20:33.11PaliI have dd backup before fsck was called
20:33.23keriocall maemo's fscks on it
20:33.45PaliI called fsck on emmc device
20:34.20Palirather create new clean filesytem
20:34.27kerioto test, i mean
20:34.29Paliand restore data
20:34.33*** join/#maemo-ssu _rd (~rd@p57B4B639.dip0.t-ipconnect.de)
20:35.20kerioPali: anyway, if there was a difference, they would've put a way to specify the filesystem features in `e2fsck`
20:36.21keriomost likely, we have a crap version of e2fsprogs
20:37.37Palihm, now called fsck -n on desktop on that dd backup and it wrote only small number of Inode XYZ was part of the orphaned inode list
20:37.58Palithis looks like on maemo is really crap version of e2fsprogs
20:38.07kerio"crap" = old
20:38.34Palifreemangordon: it looks like we need new version of e2fsprogs in cssu...
20:39.18kerioi don't think e2fsprogs has particular library requirements
20:39.37kerioit *might* be as simple as grabbing the latest debian source package and compiling it
20:51.41*** join/#maemo-ssu Woody14619b (~Woody@2620:4:4000:11:cde8:f755:5dd8:8bb0)
20:58.02Palikerio: on desktop fsck fixed that dump without any problems (it removed only 10 inodes which was orphaned)
20:58.18Palishould now I dd that dump back to n900 eMMC?
20:58.26keriojust put the files back
20:58.31keriomake a new fs from the desktop
20:58.47Paliok
21:08.38*** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn)
21:19.13ShadowJKPali; re."fs was mountable before calling fsck", I've discovered it often behaves like that on flash
21:19.59PaliShadowJK, fsck in check mode show me error that manual fix is needed
21:20.19Paliso I called fsck -y from backupmenu
21:20.30Paliand this totally damaged filesystem...
21:20.36ShadowJKyes.
21:21.03PaliI called desktop version of fsck on cloned dd image
21:21.32Paliand on desktop (new) fsck version fixed filesystem without problem
21:22.09PaliShadowJK: so in maemo we have old version of fsck which cannot recover errors in ext3
21:22.46ShadowJKI think it just gets confused by the way flash corrupts data
21:23.08keriostill, a newer e2fsck might get confused less
21:23.21kerioShadowJK: it's not like it wasn't corrupt to begin with, though
21:23.22keriois it
21:23.49kerioyou just didn't notice
21:23.50ShadowJKYeah but the kernel seems to often deal with it better
21:38.12*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
22:01.46*** join/#maemo-ssu arcean (~arcean@apn-77-112-67-219.dynamic.gprs.plus.pl)
22:06.57Palikerio: I pushed ke-recv and upstart packages to cssu-devel
22:07.10Palisource code is on gitorious in my cloned repos
22:07.30kerioi'll test them tomorrow morning before uni, if i remember to do so
22:07.35Paliyou can test static fstab, fsck on non ext3 parts, ...
22:07.49kerioalright
22:08.11Palinow rcS-late generating correct fstab for maemo copied to eMMC
22:30.02*** join/#maemo-ssu M4rtinK (~M4rtinK@46.227.13.46)
23:11.47*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.