I've read that DrivePool should correctly handle bringing up drives in the pool as needed, but if a full directory is done, all drives may have to be powered up and this can take some five seconds per drive.
Right now I'm on my second server build with W8.1 Pro as the host. Right now this server has 18 drives, ten of which are in one drive pool, containing audio and video media, to the tune of about 34T, mirrored.
Most of the time there is no issue, but occasionally after several hours away from the computer I'll still have a window open to one of the media directories, and then proceed to drag-'n-drop copy to that folder. If the copy contains a bunch of smaller files like an album, it will copy one or two, and then stop. I've waited up to 15 minutes for it to do something, but nothing happens and I cannot close the window of the open folder, though I can kill the copy process.
I see something similar occasionally when after a long time (sufficient for all-drive power down) I open a folder to the top level of the pool. I can see its directory (probably cached) but trying to access a sub directory, I get the same behavior.
This suggests one or more drives not powering up appropriately, or DP somehow not aware that it/they did.
Is any of this familiar? I'm not running the scanner, and the service for it is currently disabled (that'll be another issue I'll post about in a few days). Both of these are the latest V2 BETA's (on the web site).
The drives are all Seagate 3T or 4T and one WD 3T. Mostly 4T's are used.
Question
bblue
I've read that DrivePool should correctly handle bringing up drives in the pool as needed, but if a full directory is done, all drives may have to be powered up and this can take some five seconds per drive.
Right now I'm on my second server build with W8.1 Pro as the host. Right now this server has 18 drives, ten of which are in one drive pool, containing audio and video media, to the tune of about 34T, mirrored.
Most of the time there is no issue, but occasionally after several hours away from the computer I'll still have a window open to one of the media directories, and then proceed to drag-'n-drop copy to that folder. If the copy contains a bunch of smaller files like an album, it will copy one or two, and then stop. I've waited up to 15 minutes for it to do something, but nothing happens and I cannot close the window of the open folder, though I can kill the copy process.
I see something similar occasionally when after a long time (sufficient for all-drive power down) I open a folder to the top level of the pool. I can see its directory (probably cached) but trying to access a sub directory, I get the same behavior.
This suggests one or more drives not powering up appropriately, or DP somehow not aware that it/they did.
Is any of this familiar? I'm not running the scanner, and the service for it is currently disabled (that'll be another issue I'll post about in a few days). Both of these are the latest V2 BETA's (on the web site).
The drives are all Seagate 3T or 4T and one WD 3T. Mostly 4T's are used.
Any comments or advice?
--Bill
Link to comment
Share on other sites
6 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.