From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: *** Some devices missing ***
Date: Wed, 7 Dec 2016 08:15:36 +0000 (UTC) [thread overview]
Message-ID: <pan$6949e$51eae740$77212edf$466e5cc6@cox.net> (raw)
In-Reply-To: 004e03916ff78571800ae947487813d3@tango.lu
Luescher Claude posted on Tue, 06 Dec 2016 14:00:28 +0100 as excerpted:
> The server was running 3.13 kernel and btrfs progs 4.0 until it
> crashed. After that mounting the file system hang forever so I decided
> to switch to Linux Kernel 4.8.11 and btrfs-progs v4.8.5.
>
> There are of course no missing devices. This is what I get in dmesg
> when I try to mount the array with or without the degraded option:
> [363.066379] BTRFS error (device sdf): super_num_devices 10 mismatch
> with num_devices 9 found here
> I only find an old 2014 list entry that it was some bug and fixed so it
> should be long time fixed in 4.8.5. I need to put the device back to
> operation as soon as possible. Anybody have any further ideas what can I
> do?
FWIW there's a very recent (within the last week) thread on this, with a
patch. I'm not a dev, just a btrfs user and list regular, so I didn't
specifically track it, but someone else will likely post a more direct
link or list the thread name anyway.
IIRC the problem is that under certain circumstances the number of
devices as given in the superblock can be incorrect, so the patch lets
btrfs ignore the given number if all chunks (both copies in raid1/10
mode) appear to be accounted for on already available devices.
I believe the patch has been queued, but isn't in a release yet.
--
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-12-07 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 13:00 *** Some devices missing *** Luescher Claude
2016-12-07 8:15 ` 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$6949e$51eae740$77212edf$466e5cc6@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).