While using the rsync command to copy a disk I forgot the trailing slash and as a result created a disk4 top level folder on my disk6.

Unraid automatically created a user share called disk4.

If I were to try and create this share through the GUI I wouldn't be allowed since disk4 is a reserved name.

 

It caused confusion when I shared the disk so that I could verify it was empty in windows.

Windows showed the disk4 user share which was full not the disk4 disk share that was empty.

It took a while to figure out what had happened so that I was confidant my disk was empty.

 

I'm just wondering if auto creation of user shares should be checking against reserved names?

 

Thanks

 

Running  6.0-beta14b

While using the rsync command to copy a disk I forgot the trailing slash and as a result created a disk4 top level folder on my disk6.

Unraid automatically created a user share called disk4.

If I were to try and create this share through the GUI I wouldn't be allowed since disk4 is a reserved name.

 

It caused confusion when I shared the disk so that I could verify it was empty in windows.

Windows showed the disk4 user share which was full not the disk4 disk share that was empty.

It took a while to figure out what had happened so that I was confidant my disk was empty.

 

I'm just wondering if auto creation of user shares should be checking against reserved names?

 

Thanks

 

Running  6.0-beta14b

 

Thank you for reporting!  This is a good edge case bug that we didn't catch in our testing.  Will report to Tom for review.

Can you give me the exact steps you took to replicate?

I still argue that, since manual creation of user shares via the gui was implemented (during v5 development), the auto-creation of user shares should be disabled - it only serves to confuse.

My comments on the OPs original thread

I issued the following command in a PuTTY session to copy disk 4 to disk 6

 

rsync -av --progress --remove-source-files /mnt/disk4 /mnt/disk6

 

Because I forgot the trailing slash a top level folder called disk4 was created on disk 6 with the contents of disk 4 below it.

 

Unraid automatically created the disk4 user share

 

Let me know if you need any further information.

I had something similar happen in 14b.  See this thread: http://lime-technology.com/forum/index.php?topic=39237.0

 

Because of a typo in designating a data path for a docker, I ended up with a /mnt/user/: (full directory path /mnt/user/:/mnt/user) directory which resulted in unRAID creating a ":" share

I still argue that, since manual creation of user shares via the gui was implemented (during v5 development), the auto-creation of user shares should be disabled - it only serves to confuse.

 

You could create user shares with the GUI long before unRAID V5.

 

Otherwise, I have similar feelings as trurl. If directories on the disks don't become user shares so they appear when browsing from your PC then the average user might not know they screwed up and that they exist and that data becomes "orphaned" so to speak.