linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs check, btrfsck, fsck.btrfs
Date: Wed, 21 May 2014 03:47:31 -0700	[thread overview]
Message-ID: <20140521034731.3f7b7764@ws> (raw)
In-Reply-To: <4QT21o01E1EMSLa01QT4fM>

On Tue, 20 May 2014 18:26:59 -0600
Chris Murphy <lists@colorremedies.com> wrote:

> That ought to be true, but at least on a systemd 212-4 system, it
> assumes the system root needs to be fsck'd before mounting it. Since
> the fs isn't mounted, fstab isn't available. And the fstab.empty file
> I found in the initramfs is in fact empty. So even with fs_passno set
> to 0, systemd is trying to run fsck.btrfs, which it fails to find,
> warns about, then moves on.
> 
> I filed that bug here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1098799

[@ Chris M, I sent this to you only first.  So this one's to the list
only, but it'll have a different message-id, so you'll probably get it
as two different messages, one to the list, one direct to you.]

Hmm... it isn't doing so here.  dracut-037, systemd-212-r4 (the -r4
indicating four gentoo package level revision bumps since the initial
in-tree release of the upstream 037 version).

But I have an install-customized dracut config (tho I no longer use
host-only as explained in my last post, to the degraded boot and
systemd thread), all kernel modules built-in, etc.  If you're running a
generic everything-including-the-kitchen-sink dracut, that might
explain it, since I guess on most filesystems (not reiserfs/xfs/btrfs,
however) it would need to be run.

-- 
Duncan - No HTML messages please, as they are filtered as spam.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

  parent reply	other threads:[~2014-05-21 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 16:56 btrfs check, btrfsck, fsck.btrfs Chris Murphy
2014-05-20 23:02 ` Duncan
2014-05-21  0:26   ` Chris Murphy
     [not found]   ` <4QT21o01E1EMSLa01QT4fM>
2014-05-21 10:47     ` Duncan [this message]
2014-05-21 15:21       ` Chris Murphy

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=20140521034731.3f7b7764@ws \
    --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).