TrueNas Core to Scale portability

[atxbyea]

Right now, you would have to manually setup the sharing with the datasets you have imported... the configuration import is the major piece to be completed and tested.

Thanks, I will be playing around a lot with the TrueNAS Scale alpha in a vm for now, the importing atleast has succeeded four times, so I believe that part of it is rock solid and wouldn't be much worried.
Thanks again for great feedback, I did try to figure out how to switch to nightly trains for Scale, but I was not able to find any documentation for it, it just sent me to the download page wherever I went, do you by chance have a short instruction on how to ? There appears to be no train-selection in the GUI atleast.

 

[morganL]

My understanding is that the NIGHTly train issue is temporarily not available due to a technical issue. I expect it will be available again next week, but will report back if not.

 

[NugentS]

Is there any further news on the migration from Core to Scale which one post put as an ETA for February 21?
I love core - but want native docker (I know want want want)

 

[morganL]

Automated migration from CORE to SCALE still has SMB sharing issues to be resolved. Resolution is expected prior to 21.06

In the meantime, the manual process is available, but a second system is recommended.

 

[NugentS]

One would suspect that my second system doesn't really count

But thank you for the update

 

[shortbus]

Automated migration from CORE to SCALE still has SMB sharing issues to be resolved. Resolution is expected prior to 21.06

In the meantime, the manual process is available, but a second system is recommended.

If I have never used SMB for transfers, am I skipping any potential problems that come from SMB transfer use?

I can't find the manual process, can someone link it?
-- is it as simple as export in core and import in scale?

In case it comes up:
from uname: 12.2-RELEASE-p3 FreeBSD 12.2-RELEASE-p3 7851f4a452d(HEAD) TRUENAS amd64

# zpool --version
zfs-2.0.2-3
zfs-kmod-v2021020800-zfs_b74f7bc59

 

[anodos]

If I have never used SMB for transfers, am I skipping any potential problems that come from SMB transfer use?

I can't find the manual process, can someone link it?
-- is it as simple as export in core and import in scale?

In case it comes up:
from uname: 12.2-RELEASE-p3 FreeBSD 12.2-RELEASE-p3 7851f4a452d(HEAD) TRUENAS amd64

# zpool --version
zfs-2.0.2-3
zfs-kmod-v2021020800-zfs_b74f7bc59

The problem is not with SMB per se. It's an issue of ZFS compatibility for permissions, extended attributes, and DOS attributes between Linux and FreeBSD. The issue just more directly impacts SMB users than people using block storage or NFSv3, but it will potentially impact AFP users and NFSv4 users.

 

[shortbus]

The problem is not with SMB per se. It's an issue of ZFS compatibility for permissions, extended attributes, and DOS attributes between Linux and FreeBSD. The issue just more directly impacts SMB users than people using block storage or NFSv3, but it will potentially impact AFP users and NFSv4 users.

Does this prevent the zpool's move from CORE to SCALE?
Can the administrator correct these permissions issues? (I understand this is not a question that can be answered for all cases)
What does the migration from CORE to SCALE process look like?
- is it zpool export, then zpool import?
- other than watching for these permission issues what else should be done?

For someone that does not use NFSv4 or SMB is the process simpler?

 

[anodos]

Does this prevent the zpool's move from CORE to SCALE?

No. It does not prevent importing the pool in other operating systems. For instance a zpool created on FreeBSD can also be imported in MacOS if requisite software is installed.

Can the administrator correct these permissions issues? (I understand this is not a question that can be answered for all cases)

It is best for an administrator to wait until the features are fully implemented. The native ZFS ACL (internal to ZFS) is preserved when the pool is imported into Linux, and it is used in various ways to grant or restrict access, but the Linux kernel / userspace utilities cannot see the ACL. You might be able to recursively chmod and reset the native ZFS ACL to reflect POSIX permissions, but this is untested and will not be a supported procedure. In the future once it's implemented, the correct procedure will be to use the correct ACL type for the dataset and use appropriate tools for managing them.

What does the migration from CORE to SCALE process look like?

I believe there is a migration document in the works.

 

[shortbus]

anodos, thank you for the information and for educating me.

 

[KLEPTOROTH]

No. It does not prevent importing the pool in other operating systems. For instance a zpool created on FreeBSD can also be imported in MacOS if requisite software is installed.


It is best for an administrator to wait until the features are fully implemented. The native ZFS ACL (internal to ZFS) is preserved when the pool is imported into Linux, and it is used in various ways to grant or restrict access, but the Linux kernel / userspace utilities cannot see the ACL. You might be able to recursively chmod and reset the native ZFS ACL to reflect POSIX permissions, but this is untested and will not be a supported procedure. In the future once it's implemented, the correct procedure will be to use the correct ACL type for the dataset and use appropriate tools for managing them.


I believe there is a migration document in the works.

Have there been any new developments since this was posted? Really want to jump on the TrueNAS Scale train as well, but am currently on FreeNAS 11.3-U5.

 

[morganL]

Have there been any new developments since this was posted? Really want to jump on the TrueNAS Scale train as well, but am currently on FreeNAS 11.3-U5.

The path would be upgrade to TrueNAS CORE 12.0-U4 (after reading release notes and removing root as owner of SMB shares)
Then install 21.06 and import the original pool

Its early days for SCALE .. still BETA and documentation is not complete. Only do if you are prepared to troubleshoot and collaborate.

 

[anodos]

ACL compatibility has been added. If you migrate, you should verify that former FreeBSD datasets have acltype of NFSv4. xattr compatibility has still not been merged yet, and this will be a deal-breaker for many SMB users thinking of migrating. I think this is due soon-ish.

 

[KLEPTOROTH]

The path would be upgrade to TrueNAS CORE 12.0-U4 (after reading release notes and removing root as owner of SMB shares)
Then install 21.06 and import the original pool

Its early days for SCALE .. still BETA and documentation is not complete. Only do if you are prepared to troubleshoot and collaborate.

ACL compatibility has been added. If you migrate, you should verify that former FreeBSD datasets have acltype of NFSv4. xattr compatibility has still not been merged yet, and this will be a deal-breaker for many SMB users thinking of migrating. I think this is due soon-ish.

Thank you both. I used both SMB and nfsv3 heavily; SMB for standard file sharing and nfsv3 for vSphere.

I imagine it will have a lot of xattr, as I also used advanced permissions set from Windows on the shares.

I just want to say excellent work guys. This move to debian based OS is very, very good. FreeBSD in my experience has been very difficult to work with, and I'm loving the upcoming support for containers and such on debian.

 

[KLEPTOROTH]

Thank you both. I used both SMB and nfsv3 heavily; SMB for standard file sharing and nfsv3 for vSphere.

I imagine it will have a lot of xattr, as I also used advanced permissions set from Windows on the shares.

I just want to say excellent work guys. This move to debian based OS is very, very good. FreeBSD in my experience has been very difficult to work with, and I'm loving the upcoming support for containers and such on debian.

It's been a few months - is there full support for upgrading from FreeNAS to TrueNAS SCALE now?

 

[haagen]

It's been a few months - is there full support for upgrading from FreeNAS to TrueNAS SCALE now?

I've been wondering that myself.
I saw a video on youtube where it seems like a piece of cake. ixsystems did hell of a job with in place upgrade. But I'm still waiting for stable release (not RC), just to be sure.

 

[KLEPTOROTH]

I've been wondering that myself.
I saw a video on youtube where it seems like a piece of cake. ixsystems did hell of a job with in place upgrade. But I'm still waiting for stable release (not RC), just to be sure.

From what I've heard and read here, that is greatly dependent on your use case scenario.

ACL compatibility has been added. If you migrate, you should verify that former FreeBSD datasets have acltype of NFSv4. xattr compatibility has still not been merged yet, and this will be a deal-breaker for many SMB users thinking of migrating. I think this is due soon-ish.

Looking at the release notes, it notes that the xattr_compat feature has been removed - does this mean there's no upgrade path from FreeNAS 11.3-U5? I checked the current feature flags on my pool and I don't see that feature there, not sure if that matters. Or have the SMB sharing issues been resolved despite this?

 

[anodos]

From what I've heard and read here, that is greatly dependent on your use case scenario.

Looking at the release notes, it notes that the xattr_compat feature has been removed - does this mean there's no upgrade path from FreeNAS 11.3-U5? I checked the current feature flags on my pool and I don't see that feature there, not sure if that matters. Or have the SMB sharing issues been resolved despite this?

The xattr compatibility issue has been addressed. Recently work was merged into ZFS to expose the DOS attributes via ioctl, but I haven't plumbed into Samba yet. This would impact the DOS readonly | archive | system | hidden bits. Apart from this, the shares should transfer over as long as you don't have random FreeBSD-specific things defined in auxiliary parameters.