From: Chris Murphy <lists@colorremedies.com>
To: Konstantin Svist <fry.kun@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: "Some devices missing" only while not mounted
Date: Thu, 21 Jan 2016 20:08:45 -0700 [thread overview]
Message-ID: <CAJCQCtRb-9UJJwNvR5=X-OVhodrsCBmpSMBgm1CvNzr4mTHTRw@mail.gmail.com> (raw)
In-Reply-To: <56A19785.6090702@gmail.com>
On Thu, Jan 21, 2016 at 7:44 PM, Konstantin Svist <fry.kun@gmail.com> wrote:
>
> Wish the FS could be "edited" to remove the phantom device to make it work..
Well that's why I'm saying it's a bug. If there's a missing device,
'btrfs dev del missing' should work. But there's no device missing for
'dev del' it's only missing for 'dev ready' which makes no sense.
I suggest filing a bug, bugzilla.kernel.org. Something like 'bogus
'some devices missing' prevents boot. And then give examples in the
summary:
- mounts OK without degraded
- btrfs check does not report missing devices
- btrfs fi show does not report missing devices
- btrfs fi show -d does report missing devices
- btrfs dev del missing reports there are no missing devices
- btrfs dev ready exit value 1, so boot always fails
I don't know what debug info is useful for this case either. Maybe
btrfs-image, btrfs-debug-tree output to a file maybe the chunk tree
has a clue about this phantom missing device.
And then once you file the bug, and post the URL here, go on the IRC
channel tomorrow (business hours U.S. time) and reference it and ask
what other information devs would want before you blow away the volume
and start over. Because presumably you need to get back to work, and
to do that at this point, baring a dev having an idea how to fix it,
you'll need to blow it away.
Make a backup while you can in the meantime.
--
Chris Murphy
next prev parent reply other threads:[~2016-01-22 3:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 19:28 "Some devices missing" only while not mounted Konstantin Svist
2016-01-21 21:25 ` Chris Murphy
2016-01-21 22:27 ` Konstantin Svist
2016-01-21 23:13 ` Chris Murphy
2016-01-22 2:44 ` Konstantin Svist
2016-01-22 3:08 ` Chris Murphy [this message]
2016-01-23 23:37 ` Konstantin Svist
2016-01-22 3:55 ` Anand Jain
2016-01-22 4:40 ` Chris Murphy
2016-01-22 5:59 ` Anand Jain
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='CAJCQCtRb-9UJJwNvR5=X-OVhodrsCBmpSMBgm1CvNzr4mTHTRw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=fry.kun@gmail.com \
--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).