From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: missing /sbin/fsck.btrfs
Date: Tue, 26 Nov 2013 07:18:20 +0000 (UTC) [thread overview]
Message-ID: <pan$8f316$eba9671d$d7cae9b2$d1c7e678@cox.net> (raw)
In-Reply-To: 13F547BC-D81C-45FB-9DC8-9C076B8605EF@colorremedies.com
Chris Murphy posted on Mon, 25 Nov 2013 23:40:49 -0700 as excerpted:
> 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.
>
> I ask due to systemd-fstab-generator seemingly getting the idea from
> Fedora 20's default /etc/fstab that btrfs should have its file system
> checked, and during offline updates, systemd tries to do this, doesn't
> find /sbin/fsck.btrfs, and then has several dozen fits.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1034563
> https://bugzilla.redhat.com/show_bug.cgi?id=862871
>
> So the question, is there supposed to be (one day) a faux
> /sbin/fsck.btrfs? Or should things always check /etc/fstab fs_passno and
> honor the fact there is really no such thing?
Just symlink/copy fsck.btrfs to (/bin/)true.
https://btrfs.wiki.kernel.org/index.php/FAQ#What.27s_the_difference_between_btrfsck_and_fsck.btrfs
Or just do the /etc/fstab fs_passno = 0 thing, which is what I did with
reiserfs, so no change in that regard here when I switched to btrfs
for most partitions.
But I'm on gentoo and haven't opted to drink the systemd koolaid yet,
so what it thinks about that I wouldn't know.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-11-26 7:18 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 [this message]
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
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='pan$8f316$eba9671d$d7cae9b2$d1c7e678@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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).