Can a ZFS Pool from Proxmox be imported into TrueNAS

Griff1962

Cadet
Joined
Sep 26, 2019
Messages
2
Trying to migrate from Proxmox to TrueNAS 12, Proxmox version 6.2-11 ZFS version 5 (no special features implemented) would like to import a multi TB ZFS Pool from Proxmox to TrueNAS 12 but I do not see any discussion around importing Linux ZFS to TrueNAS, are there any special considerations before I shutdown my Proxmox system? Can I do this? Will the Pool be usable? Will it be available via Read-Only only or can I write to the imported ZFS pool in TrueNAS, if the imported ZFS pool is available via read-only would it be smart to create ZFS snapshots of the datasets before exporting? Are there any other considerations before shutting down my Proxmox system to make the ZFS Pool more acceptable/importable to/by TrueNAS?

Any and all assistance is greatly appreciated.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
ZFS version 5
That's the filesystem version, which hasn't changed in a long time. Most likely, you have a v5000/feature flags pool, so you'll need to confirm that your feature flags are compatible (see here for details).

Generically speaking, the expectation is that TrueNAS 12.0 supports all feature flags with the exception of skein, but it's conceivable that Proxmox does something unusual.

The only real point of friction beyond that tends to be ACLs and the like, which are handled differently on Linux. I'm not familiar with the specifics, but they're stored differently and are thus incompatible.
 

Griff1962

Cadet
Joined
Sep 26, 2019
Messages
2
So based on your statements above and the data below, would make more sense to export the ZFS Pool, import it and then do a ZFS send from snap shots created in the old pool to a new pool that is being created? Just trying to make sure I don't end up with an unusable/accessible ZFS pool. Or would it make more sense to copy this data to multiple external lvm devices and then migrate that data to new FreeNAS ZFS pools once they are created?

Your right, the ZFS version information is below:

zfs-0.8.4-pve1
zfs-kmod-0.8.4-pve1

The following flags/features are in effect:

NAMEPROPERTYVALUESOURCE
Pool-Baclinheritrestricteddefault
Pool-Bacltypeoffdefault
Pool-Batimeondefault
Pool-Bavailable5.63T-
Pool-Bcanmountondefault
Pool-Bcasesensitivitysensitive-
Pool-Bchecksumondefault
Pool-Bcompressiononlocal
Pool-Bcompressratio1.00x-
Pool-Bcontextnonedefault
Pool-Bcopies
1​
default
Pool-Bcreatetxg
1​
-
Pool-BcreationWed
20-May-20​
Pool-Bdedupoffdefault
Pool-Bdefcontextnonedefault
Pool-Bdevicesondefault
Pool-Bdnodesizelegacydefault
Pool-Bencryptionoffdefault
Pool-Bexecondefault
Pool-Bfilesystem_countnonedefault
Pool-Bfilesystem_limitnonedefault
Pool-Bfscontextnonedefault
Pool-Bguid16239577119161062950-
Pool-Bkeyformatnonedefault
Pool-Bkeylocationnonedefault
Pool-Blogbiaslatencydefault
Pool-Blogicalreferenced54.5K-
Pool-Blogicalused13.8T-
Pool-Bmlslabelnonedefault
Pool-Bmountedyes-
Pool-Bmountpoint/Pool-Bdefault
Pool-Bnbmandoffdefault
Pool-Bnormalizationnone-
Pool-Bobjsetid
54​
-
Pool-Boverlayoffdefault
Pool-Bpbkdf2iters
0​
default
Pool-Bprimarycachealldefault
Pool-Bquotanonedefault
Pool-Breadonlyoffdefault
Pool-Brecordsize128Kdefault
Pool-Bredundant_metadataalldefault
Pool-Brefcompressratio1.00x-
Pool-Breferenced186K-
Pool-Brefquotanonedefault
Pool-Brefreservationnonedefault
Pool-Brelatimeoffdefault
Pool-Breservationnonedefault
Pool-Brootcontextnonedefault
Pool-Bsecondarycachealldefault
Pool-Bsetuidondefault
Pool-Bsharenfsoffdefault
Pool-Bsharesmboffdefault
Pool-Bsnapdevhiddendefault
Pool-Bsnapdirhiddendefault
Pool-Bsnapshot_countnonedefault
Pool-Bsnapshot_limitnonedefault
Pool-Bspecial_small_blocks
0​
default
Pool-Bsyncstandarddefault
Pool-Btypefilesystem-
Pool-Bused14.9T-
Pool-Busedbychildren14.9T-
Pool-Busedbydataset186K-
Pool-Busedbyrefreservation0B-
Pool-Busedbysnapshots0B-
Pool-Butf8onlyoff-
Pool-Bversion
5​
-
Pool-Bvolmodedefaultdefault
Pool-Bvscanoffdefault
Pool-Bwritten186K-
Pool-Bxattrondefault
Pool-Bzonedoffdefault
 
Top