Hi

 

The Hard drive I have the docker image on never spins down. Is this normal?

 

Is it because of dockers writing logs within the image?

 

Is there anything I can do to limit the drive spinning all the time like have it in ram via an app or is that just not possible or advisable ?

 

Thanks in advance to any helpers with this.

36 minutes ago, Lien1454 said:

The Hard drive I have the docker image on never spins down. Is this normal?

 

Yes that drive will be kept spinning any time docker is running.

 

Most people tend to put the docker.img file onto a pool (cache) by configuring the 'system' share appropriately.   This stops keeping the array drive spinning and also improves performance.

4 minutes ago, itimpi said:

 

Yes that drive will be kept spinning any time docker is running.

 

Most people tend to put the docker.img file onto a pool (cache) by configuring the 'system' share appropriately.   This stops keeping the array drive spinning and also improves performance.

So would you say an ssd is more suitable?

59 minutes ago, Lien1454 said:

So would you say an ssd is more suitable?

That is what most people seem to use for pools although it is not mandated.

24 minutes ago, itimpi said:

That is what most people seem to use for pools although it is not mandated.

Am I better off doing cache --> array

Or just cache only?

 

Thanks

7 hours ago, Lien1454 said:

Am I better off doing cache --> array

Just the reverse array -> cache, or cache only

The advantage of having the cache primary and array be a secondary with a move to cache setting is that if you ever accidentally fill the cache and the minimum free space is set correctly the excess data will go to the array, then when the cache has room, the mover will put the data back on the cache.

 

Cache only will give an out of space error when it gets below the minimum free space set.