On Fri, Jun 09, 2006 at 06:31:29PM -0400, Theodore Tso wrote:
> The potential problem with this is that system administrator may never
> realize that the filesystem is just getting silently skipped. (And a
> big fat warning printed by e2fsck doesn't help when distro's like
> Ubuntu use a graphical boot sequence that hides warning messages
> printed by e2fsck).
Yeah, you're not the only one to point this out.
> Is it really that hard to edit /etc/fstab so that the fsck pass is
> skipped?
Depends on how close you are in proximity to the console, I
suspect. Point is, something _broke_.
Regardless of the name, clearly we have a _different_
filesystem. With a clean unmount, a journaled ext3 is still a valid
ext2. With a clean unmount, an extended-attribute ext3 is still a valid
plain ext3 and a valid ext2. With a clean unmount, a dir_index ext3 is
still a valid plain ext3 and a valid ext2. An extents ext3 is NEVER a
valid plain ext3 or ext2.
What happens today if you have a filesystem in fstab that
has no fsck in /sbin (eg, we all pick the name 'ext4', it says 'ext4' in
fstab, but there is no /sbin/fsck.ext4)? Does "fsck -a" skip the
partition, or halt and fail the boot? If the latter, I suspect that the
only solution is "I hope you don't encounter this on remote machines ha
ha ha". If it skips, we have yet another reason that using the same
name is a bad thing.
Joel
--
"Sometimes when reading Goethe I have the paralyzing suspicion
that he is trying to be funny."
- Guy Davenport
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@xxxxxxxxxx
Phone: (650) 506-8127
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
