Jump to content

Lost all shares!


Recommended Posts

Currently Docker is disabled, but its Settings had 80G for docker.img (at the root of cache instead of in system share), which is much more than should be necessary. Have you had problems filling it? Making it larger won't fix that it will only make it take longer to fill (and corrupt). The usual cause of filling docker.img is an application writing to a path that isn't mapped to host storage.

 

You have your VMs using ISO share for the DOMAINDIR which is OK but it means the ISOs can't be kept separately on the array if you want your domains on faster pool.

 

Your appdata, ISO (DOMAINDIR), and system shares have files on the array. Ideally you want these all on cache and set to stay on cache so your docker/VM performance will not be impacted by parity, and so array disks can spin down since these files are always open.

 

Maybe your small cache could have all these all on cache, but you wouldn't have any room for caching user shares.

 

You have a couple of other shares set to prefer cache which means to keep them on cache. Why?

 

If you reformatted your cache pool to btrfs raid0 you would have the total space of both SSDs, but no redundancy.

 

 

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...