Package: xfsprogs
Version: 2.8.11-1
Severity: normal
Tags: patch

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.

-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-xen-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Hi Wayne,

On Tue, 2007-10-02 at 10:38 -0700, Wayne Tucker wrote:

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 Scott wrote:

Hello Nathan,

My knowledge of udev is pretty limited, so I'm not sure if that would
come into play at all.

On Tue, 2007-10-02 at 17:23 -0700, Wayne Tucker wrote:

Fair enough. I'm sure the xfs maintainers will merge this (I've
sent them some mail), & I'll upload the fixed package once they do.

cheers.