From: Karel Zak <kzak@redhat.com>
To: Tom Gundersen <teg@jklm.no>
Cc: Dave Chinner <david@fromorbit.com>,
Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: missing /sbin/fsck.btrfs
Date: Mon, 6 Jan 2014 15:55:17 +0100 [thread overview]
Message-ID: <20140106145517.GG31045@x2.net.home> (raw)
In-Reply-To: <CAG-2HqXvwHnEGp=O_pBj+Wv4Z3nBNqQCpidr7=--FPNjZAZ74g@mail.gmail.com>
On Mon, Dec 30, 2013 at 06:18:53PM +0100, Tom Gundersen wrote:
> * fsck is skipped for filesystems where the relevant helper does not
> exist, so fs_passno=1 has the same effect for xfs and btrfs
> filesystems (either way, nothing happens).
>
> That still leaves non-systemd systems and calling "fsck -A" manually.
> Maybe a good solution would be to patch fsck to adopt systemd's
> behavior, which would avoid every filesystem having to ship these
> "fake" fsck helpers? What do you think Karel?
It's already implemented for years, "fsck -A" ignores filesystems
without fsck.<type> helpers. It only complains if you explicitly
specify the device on command line (e.g. fsck /dev/sdb1).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-01-06 14:55 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
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 [this message]
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=20140106145517.GG31045@x2.net.home \
--to=kzak@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=teg@jklm.no \
/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).