Hi, Just some followup on this one ...
> Does it not work to specify in /etc/fstab that the file system should > not be checked? If no fsck is available for ubifs, which program is > used to do the fsck-ing? I thought fsck used fsck.$type to do the > actual fsck operation. This is what I'm seeing on squeeze from a couple of days ago: Checking root file system...fsck from util-linux-ng 2.17.2 fsck: fsck.ubifs: not found fsck: Error 2 while executing fsck.ubifs for /dev/root done. So it is indeed ignoring the fstab option I set for it: /dev/root / ubifs defaults,noatime,rw 0 0 As to your question about fsck.ubifs, the answer to that can be found in linux/Documentation/filesystems/ubifs.txt, the relevant part being: Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts. It does not need stuff like fsck.ext2. UBIFS automatically replays its journal and recovers from crashes, ensuring that the on-flash data structures are consistent. It does that at boot before userspace is even entered (during the ubifs probe kernelside). So indeed, this probably should be an exception to the normal fsck.$type case, though just respecting the fstab selection would probably be enough as well. Since there are quite few devices using ubifs and shipping with Debian on them by default now, it would be nice to tick this one off for the squeeze release if we can. Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
