On Feb 16, 2014, at 12:18 PM, Hendrik Friedel <hendrik@xxxxxxxxxxxxx> wrote: > Hi Chris, > > thanks for your hint. > >> No. You said you need to recreate the file system, and only have these two devices and therefore must remove one device. You can't achieve that with raid1 which requires minimum two devices. >>> >>> -dconvert=single -mconvert=dup -sconvert=dup >> >> Actually, I'm reminded with multiple devices that dup might not be possible. Instead you might have to using single for all of them. Then remove the device you want removed. And then do another conversion for just -mconvert=dup -sconvert=dup, and do not specify -dconvert. That way the single metadata profile is converted to duplicate. > > I think it didn't work. > > btrfs balance start -dconvert=single -mconvert=single -sconvert=single --force /mnt/BTRFS/Video/ > After >10h: > btrfs balance status /mnt/BTRFS/Video/ > No balance found on '/mnt/BTRFS/Video/' > root@homeserver:~# btrfs fi df /mnt/BTRFS/Video/ > Data, RAID0: total=4.00GB, used=4.00GB > Data: total=2.29TB, used=2.29TB > System: total=32.00MB, used=256.00KB > Metadata: total=4.00GB, used=2.57GB It looks like everything is single except for 4GB of data which is still raid0. Weird. There should be a bunch of messages in dmesg during a normal/successful balance, and either something mentioned or missing might provide a clue why some chunks weren't converted. Unmounted, what do you get for btrfs check? > > Do you have an idea what could be wrong? No. I'd say it's a bug. 3.14rc3 should be out today, and might be worth a shot. Or btrfs-next. If you try again, you only need to convert the data profile. Also, 10 hours to balance two disks at 2.3TB seems like a long time. I'm not sure if that's expected. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
