On 01/08/13 12:08, Hugo Mills wrote:
I thought of using "btrfs device add" and just living with the untidy underlying devices, but an experiment with loopback filesystems shows that any data on the new device is silently obliterated (it might be nice if the docs mentioned this!)You would expect data in a different filesystem format to be integrated into an existing set of data structures? That would be... magic. :)
No, this was merging two btrfs filesystem of the same format. I hoped that, somehow, it would just add it into the tree, perhaps as another subvolume. Maybe even it might not show up in the overall volume, but could still be mounted from the partition volume. It's all about trees, right?!
Anyway, what's confused me is that one of the tutorials I found says that you should run mkfs on the new device before adding it, but experimentation shows that's just not necessary. The bogus instructions led me to believe that the contents of the new device was significant, somehow.
It would be nice if "man btrfs" had a big warning that the added device will get wiped, effectively.
Is there a cunning btrfs trick to do this? Can a btrfs filesystem be extended "backwards", if you see what I mean?No, using gparted to move it backwards into the free space is your best option here.
OK, thanks. Andrew -- 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
