Richard Brown wrote:
Cons- no fsck /
--- I'd regard that in the 'Pros' category... XFS doesn't need fsck on / or any other file system. (I just manually have to remember to change it to a link to '/bin/true', or similar, after an upgrade...)... Only thing it does is detect if a fs is present. I didn't realize it, but I had removed a file system in order to re-allocate space in the volume -- well -- never got around to recreating it, as it wasn't needed at this point (not mounting snapshots, so no need for a separate dev to hold a snapshot dir)... It WAS set in fstab as '3 0' (last to be mounted), another used to create backups was also removed, but it was in fstab as '0 0' so wouldn't have affected the boot process anyway. But the point I've made before on this -- is that the snapshot dir missing wasn't something that I would have wanted to prevent boot. Yet if I ran with the standard fsck (apparently xfs-team changed it to be posix compliant and it should return error if a listed fs doesn't mount -- and therefore prevent boot so you can't investigate what happened).... Understanding how that behavior might be desired for some -- I've never seen an environment where having the system drop into single user and not be network reachable was a good way to handle failure. Perhaps if it came up to level 2 and enabled root login only...that would be fine...but in this day when people manage systems remotely -- having the system come up in ANY shape so I can connect via network, is FAR preferable, to "refused to boot on any missing disk".... though if there is a problem, I wouldn't have issue in restricting login to 1 user at a time (even if remote)....(probably can't restrict to root, as many sites require remote login with a user id/restrict remotely root direct login.... FSCK made sense to not use file systems that by using them, could cause further corruption. But it doesn't make sense for fsck to return an error on a non-existent disk, as it's a *file system checker*, NOT a 'device presence detector' (despite that such a function has been overloaded upon the original design). If there is no FS to chck, then it isn't possible to return status. It should should exit with a 'not_run' status... Services that "don't run", don't automatically throw you into single user. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org