- Unless I'm missing something, there doesn't seem to be any way later
on to see that I set the data policy to raid1, except using
btrfs-dump-tree and checking the flags bits for the appropriate
group. Which can make things confusing if I have a bunch of btrfs
Yeah df is just a fun ball of wax in many respects. We don't take into
account
RAID and we don't subtrace space thats strictly for metadata, so there are
several things that need to be fixed for df. Thanks,
But as we have said many times... if we have different
raid types
I've just started playing around with btrfs RAID1, and I've noticed a
couple of what seem to be UI issues. Suppose I do something like
mkfs.btrfs -d raid1 -m raid1 dev1 dev2. I see the following minor
usability problems:
- Unless I'm missing something, there doesn't seem to be any way later
I don't disagree, please do keep in mind that I'm not suggesting anyone
use this in production yet.
When it's in mainline I suspect people will start using it for that.
I think the larger question here is where we want development to happen.
I'm definitely not pretending that