On Aug 7, 2011, Alexandre Oliva <oliva@xxxxxxxxxxxxxxxxx> wrote: > in very much the same way that it appears to be impossible to go > back from RAID1 to DUP metadata once you temporarily add a second disk, > and any metadata block group happens to be allocated before you remove > it (why couldn't it go back to DUP, rather than refusing the removal > outright, which prevents even single block groups from being moved?) Which also appears to be intentional. The code to suport this is right there in update_block_group_flags, but btrfs_rm_device refuses to let it do its job, denying the removal attempt right away, without any means to bypass the test. Could at least an option to bypass the test be introduced, through say a mount option, some /sys setting, whatever? -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer -- 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
