So, I don't and can't run VMs on one of my unRAID boxes, but it still creates the isos, domains shares, and still creates the libvrt folder inside system.  Useless and untidy.  It really bugs my OCD.

 

Could it be changed that these are only created when VM support is turned on?

I didn't think that it did (but, once either docker or vms are enabled, those shares are created)  If you run docker or vm's and prefer your own shares, nothing states anywhere that you have to use the default system ones.

 

If it really annoys you over the network, just set them to be not exported.

 

If you look at where unRaid was, where it is today, and where it is presumably going, some sort of system folder created automatically on the array is going to be required soon no matter what.  Really not too much different than all of the folders Windows makes on your C drive.

Edited March 21, 20179 yr by Squid

It does, I just booted up a fresh install of unRAID, on an AM1 system that doesn't do VMs.  The shares were created.

This always annoyed the crap out of me too so when I do a clean install I make sure I go in and turn off VMs and Docker prior to adding a single disk so it doesn't create those shares.

 

So maybe a solution is to have VM's and Docker set to off by default and let the end user enable them if they so choose rather than assuming everyone wants those shares by having them on by default.

VMs and Docker are key features of the software and most users will want to at least try them out if the hardware supports it.  Setting up those shares makes this process easier for those folks.  Leaving the services on by default increases that simplicity.  If we don't, this puts more onus on the user to have to manually generate them and create settings for them within VM Manager and Docker Manager.  If you don't want those shares because you are not using those features, just delete them and they won't regenerate unless you once again enable those services.

 

Also, the domains and system shares are set to NOT export over the network (SMB, AFP, or NFS) by default, so they shouldn't add any clutter to that usage

"If we don't, this puts more onus on the user to have to manually generate them and create settings for them within VM Manager and Docker Manager. "

 

I thought that wasting 30GB of cache space could be avoided for those not using Docker or VMs.  

 

Surely it's not difficult for unRAID to generate the Docker image and the VM associated files/share once Docker or VMs are turned on in Settings?

 

For example, if someone were wanting to use a small SSD for cache on their unRAID box, almost half a 64GB SSD is wasted with stuff they won't need.  Not all users will be able or willing to remove those images.

Related to HellDiverUK's suggestion, I actually want the system share but don't have it.

I'm not finding guidance on setting up non-user (system) shares for system, domains, and appdata. 

I have Unraid 6.9.2, and it has been upgraded over the years from the early days (pre 5.0, pre VM and fancy docker support) as time marched on. 

 

For me, appdata is a user share, and in there I see the docker.img file.  I'd really like to reorganize these "system" things more along the lines of SpaceInvaderOne's videos in how he describes the "Part 4 multiple cache pools" video.

 

I've today moved it to modern hardware.  The previous hardware was an Intel core 2 duo 4GB machine.  So it ran Docker, but not VMs (and don't think it had virtualization support at the CPU level anyway). Now I'm planning on enabling VM so I can pass thru my Windows 11 setup which is on a 1GB nvme SSD (or truly virtualize it so I can use the ssd as a cache drive and leverage that 80% of free space on it for other things coupled with the VM/appData backup plugins).  May also buy another drive for 2nd cache but only have one M2 nvme connector so it would be SATA.

 

Anyway, any guidance on setting up the missing system shares would be appreciated!

 

6 minutes ago, zaker said:

any guidance on setting up the missing system shares would be appreciated!

Attach diagnostics to your NEXT post in this thread

Sure, here you go! Note that I have a parity sync/data rebuild in progress as I'm upgrading my parity to a 2nd, bigger parity drive.

Any thoughts as to why the non-user shares are missing and how to resolve is appreciated.

.backup-diagnostics-20220317-1435.zip

2 minutes ago, zaker said:

Any thoughts as to why the non-user shares are missing and how to resolve is appreciated.

You're not using them.

 

VM service references it, but it's currently disabled.  Docker image (which the defaults go to the system share, you've got instead going to disk2 / appdata

The main thing you don't have is a fast pool (cache) for your docker/VM shares to live on so they will perform better and not keep array disks spunup.

@trurl yes that is something I plan to address, though that may not have been clear in the message a few hours ago.
@Squid yes, that is the symptom I'm describing. I need you to tell me the cure :).  VM service is not enabled yet for above explanations. Nobody has bothered to explain that anywhere AFAICT.  Perhaps if I just enable it, things automagically happen? How would it know to put it on a cache? etc.

The shares for docker get created according to your settings for Docker. Go to Settings - Docker and you will see exactly what Squid means.