From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID0 wrong (raw) device?
Date: Fri, 14 Aug 2015 09:32:11 +0200 [thread overview]
Message-ID: <20150814073211.GA10650@rus.uni-stuttgart.de> (raw)
In-Reply-To: <55CCC4AB.2080600@oracle.com>
On Fri 2015-08-14 (00:24), Anand Jain wrote:
> >> root@toy02:~# btrfs filesystem show
> >> Label: data uuid: 411af13f-6cae-4f03-99dc-5941acb3135b
> >> Total devices 2 FS bytes used 106.51GiB
> >> devid 3 size 1.82TiB used 82.03GiB path /dev/drbd2
> >> devid 4 size 1.82TiB used 82.03GiB path /dev/drbd3
> >
> > And now, after a reboot:
> >
> > root@toy02:~/bin# btrfs filesystem show
> > Label: data uuid: 411af13f-6cae-4f03-99dc-5941acb3135b
> > Total devices 2 FS bytes used 119.82GiB
> > devid 3 size 1.82TiB used 82.03GiB path /dev/drbd2
> > devid 4 size 1.82TiB used 82.03GiB path /dev/sde
> >
> > GRMPF!
>
> pls use 'btrfs fi show -m' and just ignore no option or -d if fs is
> mounted, as -m reads from the kernel.
There is now a new behaviour: after the btrfs mount, I can see shortly the
wrong raw device /dev/sde and a few seconds later there is the correct
/dev/drbd3 :
root@toy02:/etc# umount /data
root@toy02:/etc# mount /data
root@toy02:/etc# btrfs filesystem show
Label: data uuid: 411af13f-6cae-4f03-99dc-5941acb3135b
Total devices 2 FS bytes used 109.56GiB
devid 3 size 1.82TiB used 63.03GiB path /dev/drbd2
devid 4 size 1.82TiB used 63.03GiB path /dev/sde
Btrfs v3.12
root@toy02:/etc# btrfs filesystem show
Label: data uuid: 411af13f-6cae-4f03-99dc-5941acb3135b
Total devices 2 FS bytes used 109.56GiB
devid 3 size 1.82TiB used 63.03GiB path /dev/drbd2
devid 4 size 1.82TiB used 63.03GiB path /dev/drbd3
Btrfs v3.12
root@toy02:/etc# btrfs filesystem show -m
Label: data uuid: 411af13f-6cae-4f03-99dc-5941acb3135b
Total devices 2 FS bytes used 109.56GiB
devid 3 size 1.82TiB used 63.03GiB path /dev/drbd2
devid 4 size 1.82TiB used 63.03GiB path /dev/drbd3
Btrfs v3.12
Still, the kernel sees 3 instead of (really) 2 HGST drives:
root@toy02:/etc# hdparm -I /dev/sdb | grep Number:
Model Number: HGST HUS724020ALA640
Serial Number: PN2134P5G2P2AX
root@toy02:/etc# hdparm -I /dev/sde | grep Number:
Model Number: HGST HUS724020ALA640
Serial Number: PN2134P5G2P2AX
root@toy02:/etc# hdparm -I /dev/sdd | grep Number:
Model Number: HGST HUS724020ALA640
Serial Number: PN2134P5G2P2XX
--
Ullrich Horlacher Informationssysteme und Serverbetrieb
IZUS/TIK E-Mail: horlacher@rus.uni-stuttgart.de
Universitaet Stuttgart Tel: ++49-711-68565868
Allmandring 30a Fax: ++49-711-682357
70550 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<55CCC4AB.2080600@oracle.com>
next prev parent reply other threads:[~2015-08-14 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 13:07 RAID0 wrong (raw) device? Ulli Horlacher
2015-08-12 17:03 ` Chris Murphy
2015-08-12 17:43 ` Hugo Mills
2015-08-12 17:53 ` Chris Murphy
2015-08-13 12:11 ` Ulli Horlacher
2015-08-13 7:34 ` anand jain
2015-08-13 12:02 ` Ulli Horlacher
2015-08-13 14:55 ` Ulli Horlacher
2015-08-13 16:24 ` Anand Jain
2015-08-14 7:32 ` Ulli Horlacher [this message]
2015-08-15 0:02 ` Anand Jain
2015-08-15 10:09 ` Ulli Horlacher
2015-08-13 11:44 ` Austin S Hemmelgarn
2015-08-13 12:06 ` Ulli Horlacher
2015-08-13 22:32 ` Gareth Pye
2015-08-13 22:54 ` Hugo Mills
2015-08-13 23:29 ` Gareth Pye
2015-08-14 11:26 ` Austin S Hemmelgarn
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=20150814073211.GA10650@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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).