I tried Scale as an experiment, but the overhead of Kube for my little atom was too much.
I know it isn’t supported, but if I go back to a BSD based system (e.g. Core) will the pool be recognised?
I’m happy for a 100% clean restart, but obviously, I’d like to be able to get my pool back
I guess the main issue is that the ZFS version on the system I switch to should be at least as up to date as the ZFS currently running in Scale? Is that the only issue (given that I’m happy to have a clean system other than the pool).
As for switching back to core. If you have not upgraded the pool under scale then you should be fine.
I use mirrored boot, pulled one SSD off, migrated to scale, data pool imported but took 15 minutes, unhappy, replaced the scale boot SSD with the core mirror and I am back to business.
Finally got round to this. Sadly it looks like I must have succumbed to the UI nagging me and upgraded the pool (under core):
status: The pool can only be accessed in read-only mode on this system. It
cannot be accessed in read-write mode because it uses the following
feature(s) not supported on this system:
org.openzfs:zilsaxattr (Support for xattr=sa extended attribute logging in ZIL.)
I tried exporting under scale first, but same result.
Importing now back under scale… (seems to be working fine).
Thanks all for tips. I’ve decided to basically run nothing on my NAS except NFS / have a dedicated ‘server’ on top of that.