- Closed
Following on from a question posted to the 7.00 announcement thread: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-700-beta1-available-r3035/page/8/?tab=comments#comment-28893
I've created a RAIDZ2 pool where I can make shares that get Exclusive access by default - Exclusive set in general preferences and the files are only accessed in the one pool, no secondary storage.
When reassigning the location/pool for an existing share that is currently on the traditional array. Such a share has Exclusive = NO. That doesn't change to Yes when I reassign its location to the ZFS pool and set secondary storage to none.
Can this limitation be remedied such that we gain exclusive access when making this change?
Testing
There is no more array and no more cache drive, all former array drives and cache are now Unassigned
There is only the ZFS pool and all shares point only to their folders on the zpool. No secondary storage for any of them.
- Exclusive is still NO for previous shares that used to point to multiple drives*
- Exclusive is YES for previous shares that used to point to only one drive
- and YES for any new shares I create
- * appdata used to only exist on a single cache drive, but still comes up NO, unlike aShare, etc.
Exclusive shares are marked below with a small triangle next to the pool name
Diagnostics attached