I am evaluating the DrivePool version 2.2.3.1019 and I encountered issue with the duplication feature. According to the manual, the duplication should ensure that the duplicated data exist on at least two physical drives however in my testing it happily stored the secondary copy on another volume belonging to the same physical drive as the volume containing the first copy.
I created a pool from four volumes where three of them reside on one physical drive (3 according to the UI) and the fourth is on a different physical drive (2). The volume residing on the physical drive 2 had a fairly low amount of free space (116 GB) however that amount would be sufficient to store all the data used in the test. Initially the pool had no duplication enabled. I used the pool to store about 87 GB of test files. Then I did play with the balancing settings which did shuffle the data somewhat between the two biggest volumes residing on the physical drive 3 without using the volume from physical drive 2. Afterwards I enabled duplication for the entire pool. I expected that the pool will store the 87 GB of the duplicate data on the volume located on the physical drive 2 as all other volumes belong to the physical drive 3 so they do not provide any protection from drive failure however to my surprise it only stored a subset of the files with size of about 26 GB which is shown in both the UI and when examining content of the PoolPart folder on that volume while rest of the duplicates was stored on another volume stored on the physical drive 3. I am assuming that this is some bug in the duplication or balancing logic.
Question
Komat
Hi
I am evaluating the DrivePool version 2.2.3.1019 and I encountered issue with the duplication feature. According to the manual, the duplication should ensure that the duplicated data exist on at least two physical drives however in my testing it happily stored the secondary copy on another volume belonging to the same physical drive as the volume containing the first copy.
I created a pool from four volumes where three of them reside on one physical drive (3 according to the UI) and the fourth is on a different physical drive (2). The volume residing on the physical drive 2 had a fairly low amount of free space (116 GB) however that amount would be sufficient to store all the data used in the test. Initially the pool had no duplication enabled. I used the pool to store about 87 GB of test files. Then I did play with the balancing settings which did shuffle the data somewhat between the two biggest volumes residing on the physical drive 3 without using the volume from physical drive 2. Afterwards I enabled duplication for the entire pool. I expected that the pool will store the 87 GB of the duplicate data on the volume located on the physical drive 2 as all other volumes belong to the physical drive 3 so they do not provide any protection from drive failure however to my surprise it only stored a subset of the files with size of about 26 GB which is shown in both the UI and when examining content of the PoolPart folder on that volume while rest of the duplicates was stored on another volume stored on the physical drive 3. I am assuming that this is some bug in the duplication or balancing logic.
Link to comment
Share on other sites
0 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.