Hi Wayne, On Tue, 2007-10-02 at 10:38 -0700, Wayne Tucker wrote: > > > fsck.xfs doesn't check to see if the device it is asked to check > exists. This can result in a system booting with an incomplete set of > filesystem mounts. The included patch works for me, although I only > have a limited number of systems on which to test it.
Hmm, OK - seems safe enough I guess. It'd be nice to understand the root cause here a bit - is the problem that we dont attempt to access /dev/foo at all, so udev doesn't see any requests for that device and doesnt create the device node? Then later when we try to mount, the mount userspace code gets ENODEV? If so, I wonder why the mount doesn't populate the device nodes on its access? Also, the NFS fsck program is also a shell script, I wonder if it might suffer similar issues and need a similar patch? Possibly not since theres no local device involved there. I'll send the patch upstream and solicit their thoughts as well. thanks. -- Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
