From: M G Berberich <btrfs@oss.m-berberich.de>
To: linux-btrfs@vger.kernel.org
Subject: “Bug”-report: inconsistency kernel <-> tools
Date: Tue, 28 Aug 2012 21:52:44 +0200 [thread overview]
Message-ID: <20120828195244.GA15021@invalid> (raw)
Hello,
We had set up a btrfs-fs over 6 hot-plugable SAS-disks for
testing and got it into a state where kernel and btrfs-tools do not
agree any more about the state of the filesystem.
We do not remember exaclty what we did, but roughly it was something
like this (on the running system). THIS IS FROM MEMORY!
(1) pulled out one disk
(2) removed disk from btrfs
(3) rebalanced btrfs
(4) pulled out another disk
(5) removed disk from btrfs
(6) rebalanced btrfs
This went fine sofar.
(7) reinserted disk (and rebooted)
At some point before reboot the first 10 sectors of one disk
were zeroed to test if the disk gets removed from the btrfs.
Now btrfs-tools showed:
---------------------------------------------------------------------------
# btrfs fi show
failed to read /dev/sr0
Label: 'BTRFS_RAID' uuid: 807193fd-17de-4088-9a54-3e7cacdc89db
Total devices 6 FS bytes used 3.07GB
devid 4 size 931.00GB used 75.00GB path /dev/sdf
devid 5 size 931.00GB used 324.03GB path /dev/sde
devid 6 size 931.00GB used 83.03GB path /dev/sdd
devid 3 size 931.00GB used 326.03GB path /dev/sdc
devid 2 size 931.00GB used 326.03GB path /dev/sdb
devid 1 size 931.00GB used 324.04GB path /dev/sda
Btrfs Btrfs v0.19
---------------------------------------------------------------------------
As far as we can tell, only four of the disks are considered part of
the btrfs by kernel. There were only four “btrfs: bdev”-lines in dmesg
and only four disks took part in balancing. “btrfs device scan” says:
unable to scan the device '/dev/sdd' - Device or resource busy
and balance does not balance theses two devices (of 6)
It was neither possible to remove the disk from the btrfs via “btrfs
device delete” nor adding them via “btrfs device add”.
(8) a colleague swaped the two disk
Now btrfs-tools showed:
---------------------------------------------------------------------------
# btrfs fi show
failed to read /dev/sr0
Label: 'BTRFS_RAID' uuid: 807193fd-17de-4088-9a54-3e7cacdc89db
Total devices 5 FS bytes used 3.01GB
devid 6 size 931.00GB used 83.03GB path /dev/sdf
devid 4 size 931.00GB used 75.00GB path /dev/sdd
devid 5 size 931.00GB used 325.03GB path /dev/sde
devid 3 size 931.00GB used 326.03GB path /dev/sdc
devid 2 size 931.00GB used 325.03GB path /dev/sdb
devid 1 size 931.51GB used 326.04GB path /dev/sda
Btrfs Btrfs v0.19
---------------------------------------------------------------------------
Claiming the btrfs has 5 disk, but listing 6 disks out of 5 (6 of 5).
He finally managed to get the btrfs complete again by overwriting the
first 100G of the two disk. After this the btrfs-tools (correctly)
stated a filesystem with 4 disk and it was possible to add the two
disk again.
Assumption:
kernel and btrfs do not share the same view of the filesystem.
In this state commands to repair the filesystem do not work, because
they are either rejected by the tools or by the kernel.
A tool that allows a disk/partition to be marked as not-a-btrfs-part
would be nice.
A “/proc/btrfs” showing the kernels view of the filesystem would be
usefull.
MfG
bmg
--
„Des is völlig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!“ | berberic@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic
next reply other threads:[~2012-08-28 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 19:52 M G Berberich [this message]
2012-08-30 18:24 ` “Bug”-report: inconsistency kernel <-> tools Goffredo Baroncelli
2012-08-30 18:37 ` Hugo Mills
2012-08-31 19:08 ` Goffredo Baroncelli
2012-08-31 21:37 ` [BTRFS-PROGS][BUG][PATCH] Incorrect detection of a removed device [was Re: “Bug”-report: inconsistency kernel <-> tools] Goffredo Baroncelli
2012-09-11 17:31 ` [RESPOST][BTRFS-PROGS][PATCH] btrfs_read_dev_super(): uninitialized variable Goffredo Baroncelli
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=20120828195244.GA15021@invalid \
--to=btrfs@oss.m-berberich.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).