On Thu, Mar 06, 2008 at 11:23:47AM -0600, Dave Kleikamp wrote: > Zero tells fsck not to check the filesystem during reboot. It's what > tells fsck -A which filesystems to check. If we don't expect the > filesystem to be check-able during that phase, a non-zero value won't > have any real meaning. I'm now beginning to understand why SuSE wanted fsck -M/-m (ignore mounted filesystems). Looks like SuSE has a very strange and non-standard usage scenario with fsck -A which is *not* just at boot-time. So before we try to figure out whether Yet Another FSCK option makes sense, maybe it would be good to get an explanation exactly *how* SuSE is using fsck -A, besides just at boot-time? - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
