From: Florian Uekermann <florian@uekermann.me>
To: linux-btrfs@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Device only missing if unmounted
Date: Sat, 13 Dec 2014 15:24:56 +0100 (CET) [thread overview]
Message-ID: <932711394.78334.1418480696257.JavaMail.open-xchange@patina.store> (raw)
In-Reply-To: <5487B3FB.4070109@oracle.com>
Dear Anand,
thank you for your help.
> On December 10, 2014 at 3:46 AM Anand Jain <anand.jain@oracle.com> wrote:
> It depends on the disk that is read first, you could read super block
> using btrfs-show-super and check if num_device.
I checked this for all three devices and num_devices is 4 for all of them.
The full output is below.
> It may fail if you are mounting more than one subvol during boot and if
> you don't have this patch.
>
> commit 0f23ae74f589304bf33233f85737f4fd368549eb
> Author: Chris Mason <clm@fb.com>
> Date: Thu Sep 18 07:49:05 2014 -0700
>
> Revert "Btrfs: device_list_add() should not update list when mounted"
>
> This reverts commit b96de000bc8bc9688b3a2abea4332bd57648a49f.
I am running 3.18-rc5+ from linus tree. If I am not mistaken,
that commit is his tree in since 3.17-rc6.
So I guess the question is: Why does the superblock say
num_devices=4 (and how do I fix it)?
Or am I misunderstanding the problem?
Best regards,
Florian
root@oot:/home/shared# btrfs-show-super /dev/sdb
superblock: bytenr=65536, device=/dev/sdb
---------------------------------------------------------
csum 0x55a3eb1d [match]
bytenr 65536
flags 0x1
magic _BHRfS_M [match]
fsid be2b3499-7452-4b91-b664-4ec4d7ff62b9
label
generation 3003
root 441395970048
sys_array_size 129
chunk_root_generation 3001
root_level 1
chunk_root 442469761024
chunk_root_level 1
log_root 0
log_root_transid 0
log_root_level 0
total_bytes 109927469in the first place8752
bytes_used 160703954944
sectorsize 4096
nodesize 16384
leafsize 16384
stripesize 4096
root_dir 6
num_devices 4
compat_flags 0x0
compat_ro_flags 0x0
incompat_flags 0x61
( MIXED_BACKREF |
BIG_METADATA |
EXTENDED_IREF )
csum_type 0
csum_size 4
cache_generation 3003
uuid_tree_generation 3003
dev_item.uuid 5b8c8d20-c330-48a2-814c-c6986b787d52
dev_item.fsid be2b3499-7452-4b91-b664-4ec4d7ff62b9 [match]
dev_item.type 0
dev_item.total_bytes 500107862016
dev_item.bytes_used 162168569856
dev_item.io_align 4096
dev_item.io_width 4096
dev_item.sector_size 4096
dev_item.devid 2
dev_item.dev_group 0
dev_item.seek_speed 0
dev_item.bandwidth 0
dev_item.generation 0
next prev parent reply other threads:[~2014-12-13 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 11:15 Device only missing if unmounted Florian Uekermann
2014-12-10 2:46 ` Anand Jain
2014-12-13 14:24 ` Florian Uekermann [this message]
2014-12-18 0:56 ` Anand Jain
[not found] ` <1184043001.122994.1419096721838.JavaMail.open-xchange@ptangptang.store>
2014-12-24 15:45 ` Anand Jain
-- strict thread matches above, loose matches on Subject: below --
2015-01-11 15:49 Florian Uekermann
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=932711394.78334.1418480696257.JavaMail.open-xchange@patina.store \
--to=florian@uekermann.me \
--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).