New user here, I have a drivepool configured with 6 SSD's. I have duplication turned on. If I try to build a Rust (programming language) application, when build process fails, with windows error 5. This is a very weird issue, and I've been debugging this for hours now, before I realized that drivepool is most likely the problem, since the application builds correctly on any other drives which are not part of the DrivePool. It even works on the drives which are part of the pool, if I use them directly, circumventing the DrivePool layer.
After some more debugging it turns out that the issue is connected to Read Striping. Having it on is what leads to the aforementioned errors. However I'd like to continue using Read Striping, because disabling it leads to quite a big performance loss. What can I do in this situation? Can I turn off Read Striping on a folder to folder basis? Maybe turn off duplication on this folder only so that DrivePool is forced to read from one drive? What could be the root issue here? Maybe the compiler is using memory mapped files which do not play along with DrivePool?
Question
botiapa
New user here, I have a drivepool configured with 6 SSD's. I have duplication turned on. If I try to build a Rust (programming language) application, when build process fails, with windows error 5. This is a very weird issue, and I've been debugging this for hours now, before I realized that drivepool is most likely the problem, since the application builds correctly on any other drives which are not part of the DrivePool. It even works on the drives which are part of the pool, if I use them directly, circumventing the DrivePool layer.
After some more debugging it turns out that the issue is connected to Read Striping. Having it on is what leads to the aforementioned errors. However I'd like to continue using Read Striping, because disabling it leads to quite a big performance loss. What can I do in this situation? Can I turn off Read Striping on a folder to folder basis? Maybe turn off duplication on this folder only so that DrivePool is forced to read from one drive? What could be the root issue here? Maybe the compiler is using memory mapped files which do not play along with DrivePool?
What can I do to help you debug the root issue?
Link to comment
Share on other sites
1 answer 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.