I have an issue with balancing from an SSD for which I first need to explain my configuration.
The notes for the SSD optimizer stated that if you are performing duplication, you would need to have multiple SSDs. I understand why this would be the case. I had inquired here on the forum whether I could simply partition my SSD into multiple partitions to satisfy this need but found that this is not the case. It was suggested that I could create 2 levels of pools to work around this. As a result, this is how I ended up configuring my system:
I have one drive pool that has the drive letter Y: which consists of five 8TB disks. Several of my folders are configured with a 3x duplication.
I then have a second pool that consists of my SSD and drive Y:. This pool has the drive letter Z:.
I have my balancing rules set to rebalance immediately (for now, for testing).
As a test, I drop a good-sized stack of files onto the SSD. This works great. The files get moved off of the SSD to my Y: drive where the 3x duplication is correctly applied.
However, here is my problem: One of these folders contains many small files that contain important information that I want duplicated. Because I am using this dual tier of pools, my first pool that contains the SSD and the other pool has no duplication configured. The duplication happens at the second level. As a result, it only moves files off of the SSD when the balancing rule thresholds have been met. The minimum amount of changed data that can be set for the threshold seems to be 1GB. However, as I noted, the one folder has many very small files. As a result, this trigger of 1GB is not reached leaving these files stuck on the SSD and thus not duplicated.
My question: Is this simply a limitation of my configuration or is there some way that I can force the data to be moved off of the SSD without having to wait for a 1GB threshold to be reached?
Question
hsehestedt
I have an issue with balancing from an SSD for which I first need to explain my configuration.
The notes for the SSD optimizer stated that if you are performing duplication, you would need to have multiple SSDs. I understand why this would be the case. I had inquired here on the forum whether I could simply partition my SSD into multiple partitions to satisfy this need but found that this is not the case. It was suggested that I could create 2 levels of pools to work around this. As a result, this is how I ended up configuring my system:
I have one drive pool that has the drive letter Y: which consists of five 8TB disks. Several of my folders are configured with a 3x duplication.
I then have a second pool that consists of my SSD and drive Y:. This pool has the drive letter Z:.
I have my balancing rules set to rebalance immediately (for now, for testing).
As a test, I drop a good-sized stack of files onto the SSD. This works great. The files get moved off of the SSD to my Y: drive where the 3x duplication is correctly applied.
However, here is my problem: One of these folders contains many small files that contain important information that I want duplicated. Because I am using this dual tier of pools, my first pool that contains the SSD and the other pool has no duplication configured. The duplication happens at the second level. As a result, it only moves files off of the SSD when the balancing rule thresholds have been met. The minimum amount of changed data that can be set for the threshold seems to be 1GB. However, as I noted, the one folder has many very small files. As a result, this trigger of 1GB is not reached leaving these files stuck on the SSD and thus not duplicated.
My question: Is this simply a limitation of my configuration or is there some way that I can force the data to be moved off of the SSD without having to wait for a 1GB threshold to be reached?
2 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.