From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unrecoverable fs corruption?
Date: Sun, 3 Jan 2016 16:08:35 +0000 (UTC) [thread overview]
Message-ID: <pan$9d4e3$8e43ab0$7c386064$b1282bb4@cox.net> (raw)
In-Reply-To: 20160102115318.4e76f773@hydra
Alexander Duscheleit posted on Sat, 02 Jan 2016 11:53:18 +0100 as
excerpted:
> I was under the impression that a mount (actually any) command issued
> against a member of a multi-device btrfs would affect the whole
> multi-device.
Well, yes and no. Yes, when it mounts correctly.
But with a multi-device btrfs, it can happen that btrfs doesn't yet know
about all the devices when a mount is attempted, in which case the mount
may fail (particularly without the degraded option), simply because it
doesn't know about the other devices.
A btrfs device scan after all devices are available but before the mount
attempt should fix this problem and allow a mount with any of the
component devices, and these days, udev normally triggers that when any
new devices appear, so it seldom needs to be done manually. However, in
udev-free cases or in early boot before udev is up, udev obviously won't
handle it and the mount can still fail.
Additionally, if a device is missing or damaged to the point that btrfs
can't see it, btrfs will normally refuse a mount unless degraded is one
of the mount options. And depending on the situation, degraded,ro may be
needed. While you mentioned below this part in your reply that you had
tried degraded,ro, that wasn't in your original post, so we wanted the
mount options you had actually tried, to see if you had tried degraded,ro,
or not.
--
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
prev parent reply other threads:[~2016-01-03 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 23:36 Unrecoverable fs corruption? Alexander Duscheleit
2016-01-01 1:22 ` Chris Murphy
2016-01-01 8:13 ` Duncan
2016-01-02 4:32 ` Christoph Anton Mitterer
2016-01-03 15:00 ` Duncan
2016-01-04 0:05 ` Christoph Anton Mitterer
2016-01-06 7:35 ` Duncan
2016-01-02 10:53 ` Alexander Duscheleit
2016-01-02 21:19 ` Henk Slager
2016-01-03 15:53 ` Duncan
2016-01-03 16:24 ` Martin Steigerwald
2016-01-03 16:08 ` Duncan [this message]
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$9d4e3$8e43ab0$7c386064$b1282bb4@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).