I agree that this issue is not a bug as long as the behaviour I
experienced is intentional.
I fully agree that in case the behaviour is intentional, it also should
be documented somewhere (including kernel versions in case of breaking
changes).
I also agree that btrfs tools' output should be
should btrfs maybe add a hint to add the "--force" option when it
refuses to do
"btrfs balance start -mconvert=raid0 /" (maybe "single" instead of
"raid0" works too?)
when i tried this command without --force, I just got "invalid argument"
only the log file suggested to use "--force"
The error as originally reported is due to btrfs converting meta and
system data to RAID1 when adding a second device to a single device
filesystem and rebalancing. You can then no longer go below 2 devices.
Check dmesg or /var/log/syslog as suggested. The remedy is to mconvert
to single and
With Ubuntu 14.04, Kernel 3.16 (from HES), I could btrfs-balance a non-
raid /dev/sda2 btrfs fs with
cd /mnt
mkdir fulldisk
mount /dev/sda2 fulldisk
btrfs device add /dev/sdb fulldisk
btrfs balance start fulldisk
btrfs device delete /dev/sdb fulldisk
But with Ubuntu 14.04, Kernel
I installed the mainline kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.4-precise/ and compiled the btrfs tools from
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git.
Then, I could remove the second drive after converting raid1 back to
raid0:
% ./btrfs balance
Suffering same problem with 4 disk setup with raid1 metadata and raid0
data. Enough free space on filesystem, added a fourth disk to replace
one with relocate pending sectors (only 56 to be exact, on a 1.5 TB
disk), tried to delete the bad one and no luck. System exercices disks a
couple of hours
I get an error when trying to remove one disk from a set of three (so metadata
could still be mirrored). This is on Precise Pangolin. I also include the
output of filesystem show, as something clearly happened here, although I'm
unsure how to interpret it.
% sudo btrfs fi show
Label:
I can also reproduce this bug, both with 10.10 (kernel 2.6.35) and 11.10
(which has 3.x)
It also fails even if you use mkfs.btrfs -m single -d single /dev/sdxx
when you create the initial device for the btrfs filesystem.
It seems to work OK if all the devices have no data on them, like if you
** Attachment added: testcase that reproduces the bug
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/880645/+attachment/2647474/+files/btrfs%20bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: btrfs-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880645
Title:
According to #btrfs on freenode, this problem occurs because balancing
the filesystem raid1 mirrors the meta data. Then you are not allowed to
remove any devices because the metadata wouldn't be raid1 mirrored any
more. The weird question that comes from this is why are you allowed to
make a btrfs
** Description changed:
What I did to cause this:
Installed ubuntu using btrtfs root.
Added a device with 'btrfs device add /dev/sda9 /'
Balanced the file system with 'btrfs filesystem balance /'
Tried to remove a device with 'btrfs device delete /dev/sda9 /'. Noticed that
I got the
** Attachment added: btrfs_bug.img_with_zeroed_files.sda8
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/880645/+attachment/2569105/+files/btrfs_bug.img_with_zeroed_files.sda8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: btrfs_bug.img_with_zeroed_files.sda9
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/880645/+attachment/2569106/+files/btrfs_bug.img_with_zeroed_files.sda9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
14 matches
Mail list logo
