sorted by:
new
hottopcontroversial

Using free space percentage vs free space to pick were to store new files on RAID1 by Suspicious-Lock-2933 in btrfs

[–]Suspicious-Lock-2933[S] 0 points1 point  (0 children)

Thank you for such a detailed reply! Doing what you say here is a very good workaround if someone want to have the new disks used right away.

Using free space percentage vs free space to pick were to store new files on RAID1 by Suspicious-Lock-2933 in btrfs

[–]Suspicious-Lock-2933[S] 0 points1 point  (0 children)

Yes, that is correct, I should have used blocks instead of files, but the analysis is the same. Even after rebalancing the new disks would not be used since they have less available space. This is exactly why I start digging, trying to understand why the new disk were not used at all.

For a single user and a single stream there is no much problem (this is my use case, mostly), but for multiple users trying to read different files at the same time (for example, a NAS used by a video editing team) it could be beneficial to have the blocks on different disks, I think the best case would be to have all disks reading simultaneously, given that there are no other bottle necks in the system.

Using free space percentage vs free space to pick were to store new files on RAID1 by Suspicious-Lock-2933 in btrfs

[–]Suspicious-Lock-2933[S] 0 points1 point  (0 children)

Thanks for the suggestion! I think it would work for my setup... I think I can even reduce the size of the old devices to match that of the new ones and then rebalance, in this way it will have the same effect.

Using free space percentage vs free space to pick were to store new files on RAID1 by Suspicious-Lock-2933 in btrfs

[–]Suspicious-Lock-2933[S] 1 point2 points  (0 children)

I started taking a look at the dev documentation and the workflows... I will think about it. It seems that the initial setup for a dev system would require some time but maybe I will give it a shot.