From: Dave Chinner <david@fromorbit.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: missing /sbin/fsck.btrfs
Date: Wed, 27 Nov 2013 11:51:26 +1100 [thread overview]
Message-ID: <20131127005126.GC10988@dastard> (raw)
In-Reply-To: <13F547BC-D81C-45FB-9DC8-9C076B8605EF@colorremedies.com>
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....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-11-27 0:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 6:40 missing /sbin/fsck.btrfs Chris Murphy
2013-11-26 7:18 ` Duncan
2013-11-26 7:53 ` dima
2013-11-26 18:43 ` Chris Murphy
2013-11-26 22:36 ` Duncan
2013-11-27 4:55 ` Chris Murphy
2013-11-27 6:14 ` Duncan
2013-11-27 0:51 ` Dave Chinner [this message]
2013-11-27 3:06 ` Chris Murphy
2013-12-01 23:01 ` Dave Chinner
2013-12-30 17:18 ` Tom Gundersen
2014-01-06 14:55 ` Karel Zak
2013-11-27 11:19 ` Tom Gundersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131127005126.GC10988@dastard \
--to=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).