I have a problem with the standby (actually it's the spinup) of my drives.
Initial setting: All drives are in standby (= spinned down)
Accessing share -> Spinup of ALL drives.
You don't even have to browse through your share, opening it (e.g. mount network drive) is enough to make the drives spinup.
Why do all drives spin up?
I mean, ok, it's logical that they spin up so you get the directory etc, but why isn't there an internal drivepool cache storing the directory structure (folders, size etc)?
With a cache like this there would be no need to spin up all drives.
All clients already have a cache like this. Once you accessed your share (drives spun/span (?) up) everything is stored in this cache. Once you access your share a second time no drives spin up (when in standby).
So we need a server-side cache from which the clients can retrieve the data to build their own cache.
In my case it's very annoying: I set up a feeder disk to store all my incoming data (in a specific folder which is only allowed to store data on the feeder disk) but when I access this new data all drives do a spinup which makes the feeder this pretty useless to me.
Can you please make a server-side cache? Or something similiar, I don't know ^^
Question
Firefly
Hello,
I have a problem with the standby (actually it's the spinup) of my drives.
Initial setting: All drives are in standby (= spinned down)
Accessing share -> Spinup of ALL drives.
You don't even have to browse through your share, opening it (e.g. mount network drive) is enough to make the drives spinup.
Why do all drives spin up?
I mean, ok, it's logical that they spin up so you get the directory etc, but why isn't there an internal drivepool cache storing the directory structure (folders, size etc)?
With a cache like this there would be no need to spin up all drives.
All clients already have a cache like this. Once you accessed your share (drives spun/span (?) up) everything is stored in this cache. Once you access your share a second time no drives spin up (when in standby).
So we need a server-side cache from which the clients can retrieve the data to build their own cache.
In my case it's very annoying: I set up a feeder disk to store all my incoming data (in a specific folder which is only allowed to store data on the feeder disk) but when I access this new data all drives do a spinup which makes the feeder this pretty useless to me.
Can you please make a server-side cache? Or something similiar, I don't know ^^
Link to comment
Share on other sites
20 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.