- Solved
- Minor
Some time ago there was some logic implemented where it wasn't possible to change the number of pool slots after making any change to a pool, like after unassigning one of the devices, this still worked correctly with v6.10-rc1 but it doesn't with rc2 or newer, this can easily cause problems with the pool after some changes, just like recently a couple of users posted in the forums, example:
Start with a two device cache pool in default raid1, user decided to split the devices for use in two pools, with the array stopped:
-unassign one of the pool devices
-change that pool to just 1 slot
-leave the removed device unassigned or assign it to a new pool and start the array, device won't be deleted from the original pool, so if left unassigned it will still be part of the pool despite of what the GUI shows, if assigned to a new pool there will only be one filesystem of the two devices showing in duplicat in both pools.
In previous release after unassigning one device user can't change the number of slots, so after starting the array, with the removed device unassigned or assigned it will be deleted from the original pool making it available for use in a new one.