On Fri, Jun 09, 2006 at 03:47:00PM -0700, Joel Becker wrote: > 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". It will halt and fail the boot. Of course, installing a kernel more recent on 2.6.14 or so a RHEL4 system when you have a SCSI controller such as MPT Fusion will also cause the system to fail to boot unless you remember to compile it directly into the kernel because of changes in semantics about whether the SCSI probing happens before or after the module load completes --- and the answer that has been given is "we don't care". So these sorts of traps have been around for people who are going back and forth between the bleeding edge and distro systems, but I think we'd all agree that this isn't necessarily the common case. - Ted - 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
