phhowe17 Posted February 26, 2023 Posted February 26, 2023 My first thought was using the Balancing -> Fileplacement option and removing the disk from each of the top level folders. But that doesn't stop someone (well, not me!) from creating a new top level folder structure. Quote
0 Doug Posted February 27, 2023 Posted February 27, 2023 Looks like this topic may answers your question. Quote
0 Shane Posted February 27, 2023 Posted February 27, 2023 Marking a pooled drive read-only may cause drivepool to not write to the pool at all? EDIT: can cause it to complain that the disk is write-protected if an operation on the pool involves that disk. My suggestion (assuming otherwise defaults) would be: Manage Pool -> Balancing... -> Balancers tab -> Ordered File Placement plugin -> move the problem drive to the bottom -> select "Only control new file placement". Manage Pool -> Balancing... -> Settings tab -> tick "File placement rules respect real-time file placement limits set by the balancing plugins" This should still allow other disks in the pool to be written. Quote
0 Christopher (Drashna) Posted March 1, 2023 Posted March 1, 2023 You could set the volume or drive as read only, but you may run into write errors when doing that. What has been outlined above is probably best. Quote
Question
phhowe17
My first thought was using the Balancing -> Fileplacement option and removing the disk from each of the top level folders. But that doesn't stop someone (well, not me!) from creating a new top level folder structure.
3 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.