April 29, 20206 yr Community Expert Only the first one will be accessible when using the user share, both can be accessed when using the disk share.
April 29, 20206 yr Community Expert 28 minutes ago, cinereus said: What happens if you have a file e.g. user/share/file (stored as /disk1/share/file) and you then create a file at /disk2/share/file? Unraid will only show one of them (I think the one on the lowest number disk) at the User Share level. You can now get some unexpected behaviour because if you delete/rename/move the first file at first glance the file seems to still be there. Actually you are now seeing the second copy as the first copy is no longer masking the second one.
May 2, 20206 yr On 4/29/2020 at 12:09 PM, itimpi said: Unraid will only show one of them (I think the one on the lowest number disk) at the User Share level. You can now get some unexpected behaviour because if you delete/rename/move the first file at first glance the file seems to still be there. Actually you are now seeing the second copy as the first copy is no longer masking the second one. Presumable the unBALANCE plugin is designed to sidestep this bug entirely? I made the mistake of trying to avoid this all by using /mnt/diskX whereas it's less neat but much simpler to work from a /mnt/user state from the beginning.
May 2, 20206 yr Community Expert 7 minutes ago, cinereus said: Presumable the unBALANCE plugin is designed to sidestep this bug entirely? Yes, internally UnBalance uses disk-to-disk moves.
October 28, 20214 yr I hate to jump in a bit late so I think I'm following. I just had a weird question related - if I delete an excluded/included and it starts writing to more than one disk (like it should eventually) when something accesses that share it will spin up both drive's correct?
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.