Importing ZFS pool from Napp-it OmniOS to Proxmox

[yu130960]

Observations:

Exported the ZFS pool (which was created in OmniOS) from OmniOS
Installed Proxmox PVE 8.35 on ssd with the HBAs attached with the ZFS drives
Proxmox automatically imported the pool (which was unexpected)
Everything else seems to work and be fine
Ran into an issue in that the shares were persisting from the ZFS pool ("zfs get -r sharesmb" and "zfs get -r sharenfs" confirmed shares)
Had to remove all zfs persisting shares and use proxmox for the shares
Quickly AI vibe coded some scripts to look after scrubs, snapshots, pruning, zfs health checks and alerts over html email.?

Any other ZFS settings that may have been set in napp-it like the above that may persist? (i.e. read only?)

 

[gea]

If you import a pool on any other system, all ZFS properties remain as defined.
Only share managemant between OmniOS and Linux behave different.

On OmniOS (and Solaris) sharesmb and sharenfs control the OS/ZFS integrated kernelbased services. On Linux there is no such nfs/smb server. For compatibilty reason there are the same properties available but they are only a marker for SAMBA or an installed NFS server so they behave different.

 

[yu130960]

Thanks Gea.

In the future, i imagine it would be best to remove all zfs shares prior to export to a Linux based system.

 

[gea]

You can set to off in Linux as well, only care about correct SAMBA (or ksmbd) settings in Linux.

 

[ThomasDHodges]

If you import a pool on any other system, all ZFS properties remain as defined.
Only share managemant between OmniOS and Linux behave different.

On OmniOS (and Solaris survival race ) sharesmb and sharenfs control the OS/ZFS integrated kernelbased services. On Linux there is no such nfs/smb server. For compatibilty reason there are the same properties available but they are only a marker for SAMBA or an installed NFS server so they behave different.

I agree with your point about why ZFS properties behave differently between OmniOS and Linux environments!