So last night I disbanded the RAID and created my new shiny pool. I thought about using Ordered File Placement, since "By Folder Placement" is not implemented (Drive Bender wanted to implement this like 3 years ago, but it did not come.) But filling-up disk by disk is not quite what I want, it's close but not quite. Why? Because I will be using one or two of the disks "outside" of the poolpart, so I do not necessarily want to fill them up - letting DrivePool use always the least-full disk ensures each disk will always be as free as possible, and this makes sense if you're going to use the disks for stuff outside of the pool folder. Enter file-placement rules. I always thought I would never need them. But it turns out I will be using them after all - I will tell DrivePool to use 2 of the 3 disks for all my data files that are normal size and duplicated (e.g. documents and the like) and it will be placing the rest (e.g. movies) where it wants. I think this will be really good - all the important data will be together, mirrored on two disks, so it will make everything simple for recovery (e.g. just like with the Ordered File Placement) but I will also have the advantage of always having the maximum amount of free space on each disk. Amazing how flexible Drivepool is.
I still wish there was a per-folder balancer, but when I think about writing one, it quickly becomes complicated - you need a "chunk size" because if a folder is 6TB in size you can't just treat it as a single entity, you need to be able to split big folders into chucks so you have some flexibility in placement and duplication. Anyway, maybe one day Alex can think about it.
Question
B00ze
Good day.
So last night I disbanded the RAID and created my new shiny pool. I thought about using Ordered File Placement, since "By Folder Placement" is not implemented (Drive Bender wanted to implement this like 3 years ago, but it did not come.) But filling-up disk by disk is not quite what I want, it's close but not quite. Why? Because I will be using one or two of the disks "outside" of the poolpart, so I do not necessarily want to fill them up - letting DrivePool use always the least-full disk ensures each disk will always be as free as possible, and this makes sense if you're going to use the disks for stuff outside of the pool folder. Enter file-placement rules. I always thought I would never need them. But it turns out I will be using them after all - I will tell DrivePool to use 2 of the 3 disks for all my data files that are normal size and duplicated (e.g. documents and the like) and it will be placing the rest (e.g. movies) where it wants. I think this will be really good - all the important data will be together, mirrored on two disks, so it will make everything simple for recovery (e.g. just like with the Ordered File Placement) but I will also have the advantage of always having the maximum amount of free space on each disk. Amazing how flexible Drivepool is.
I still wish there was a per-folder balancer, but when I think about writing one, it quickly becomes complicated - you need a "chunk size" because if a folder is 6TB in size you can't just treat it as a single entity, you need to be able to split big folders into chucks so you have some flexibility in placement and duplication. Anyway, maybe one day Alex can think about it.
Regards,
Link to comment
Share on other sites
9 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.