From: Dmitrii Tcvetkov <demfloro@demfloro.ru>
To: master.b.at.raven@chefmail.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS RAID 1 not mountable: open_ctree failed, super_num_devices 3 mismatch with num_devices 2 found here
Date: Thu, 24 Aug 2017 15:24:18 +0300 [thread overview]
Message-ID: <20170824152418.542e9dfa@job> (raw)
In-Reply-To: <a49007a603563cf8d837d0ffa305fb35@email.freenet.de>
> I rebootet with HWE K4.11
>
> and took a pic of the error message (see attachment).
>
> It seems btrfs still sees the removed NVME.
> There is a mismatch from super_num_devices (3) to num_devices (2)
> with indicates something strage is going on here, imho.
>
> Then i returned and booted K4.4, which boots fine.
>
> root@vHost1:~# btrfs dev stat /
> [/dev/nvme0n1p1].write_io_errs 0
> [/dev/nvme0n1p1].read_io_errs 0
> [/dev/nvme0n1p1].flush_io_errs 0
> [/dev/nvme0n1p1].corruption_errs 0
> [/dev/nvme0n1p1].generation_errs 0
> [/dev/sda1].write_io_errs 0
> [/dev/sda1].read_io_errs 0
> [/dev/sda1].flush_io_errs 0
> [/dev/sda1].corruption_errs 0
> [/dev/sda1].generation_errs 0
>
> Btw i edited the subject to match the correct error.
>
>
> Sash
Thats very odd, if super_num_devices in superblocks don't match real number of devices
then 4.4 kernel shouldn't mount the filesystem too.
We probably need help from one of btrfs developers since I'm not one, I'm just btrfs user.
Can you provide outpus of:
btrfs inspect-internal dump-super -f /dev/sda1
btrfs inspect-internal dump-super -f /dev/nvme0n1p1
Depending on version of btrfs-progs you may need to use btrfs-dump-super instead of "btrfs inspect-internal dump-super"
>3rd i saw https://patchwork.kernel.org/patch/9419189/ from Roman. Did
>he receive any comments on his patch? This one could help on this
>problem, too.
Don't know about this patch from Roman per se, but there is a patchset[1] which is aimed to be merged in 4.14 merge window AFAIK.
[1] https://www.spinics.net/lists/linux-btrfs/msg66891.html
parent reply other threads:[~2017-08-24 12:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <a49007a603563cf8d837d0ffa305fb35@email.freenet.de>]
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=20170824152418.542e9dfa@job \
--to=demfloro@demfloro.ru \
--cc=linux-btrfs@vger.kernel.org \
--cc=master.b.at.raven@chefmail.de \
/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).