Closed mdziekon closed 6 years ago
I think this was a problem of regex. If I am not mistaken I had the fix in one branch in one of my dev vm, got left behind and didn’t push the fix. Won’t be for another 3 weeks until I get back from holidays.
I think this was a problem of regex. If I am not mistaken I had the fix in one branch in one of my dev vm, got left behind and didn’t push the fix. Won’t be for another 3 weeks until I get back from holidays.
Yes, it is a problem with the name discovery regexp, as I've already described in point 3. The fix is pretty straightforward (simply, allowing dashes in the dev name), so I can submit a PR myself if that's OK (considering that there is a patch somewhere waiting to be pushed).
Sorry I read too quickly, you’re correct you mentioned the regex. I am ok if you submit the pr, if you look at omvextras github activity you will notice we are very low on dev resources. More than welcome if you want to submit pr’s to fix bugs or add features.
Tested using:
openmediavault
: 4.1.11openmediavault-zfs
: 4.0.4Consider the following scenario:
/dev/dm-0
deviceOMVModuleZFSUtil::getDiskId
does not recognise dashes in device name regexp, it fails to properly detect the aliasing (another problem related to this detection behaviour described here: https://github.com/OpenMediaVault-Plugin-Developers/openmediavault-zfs/issues/51)Expected behaviour:
/dev/dm-0
(and so on) when creating new pools using "by-id" aliasing. Edit: to clarify - it is possible to create pools with "no aliasing" option, but this feels like it might cause troubles if a device will get decrypted in a different order than on pool creation.