On Wed, Nov 27, 2013 at 1:51 AM, Dave Chinner <da...@fromorbit.com> wrote: > On Mon, Nov 25, 2013 at 11:40:49PM -0700, Chris Murphy wrote: >> Hi, >> >> Is there supposed to be an /sbin/fsck.btrfs? I'm seeing a handful >> of threads indicating some idea of having it just do a no-op like >> fsck.xfs does, but then also the idea that /etc/fstab should >> correctly set fs_passno to 0 instead of such trickery. > > You're missing a key thing that fsck.xfs does that fstab expects to > work - it fails with an error if the device is missing. If the > device is present, then fsck.xfs returns success. > > We did this because people were having problems when devices took a > long time to instantiate (e.g. SAN, iscsi and other remote devices) > and the 'device exists' check prevents /etc/fstab trying to mount > the filesystems before they are present and then throwing a hissy > fit....
Note that this kind of stuff should no longer be necessary, at least if you use systemd (or I suppose Upstrat, but I didn't check): Filesystems will only be mounted after their backing devices appear. Cheers, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
