zfs replication inside jail and feature@large_dnode

[nico-truenas]

Hi all

I'm running a TrueNAS 12 system and I would like to replicate some zfs snaphosts to a jail hosted on another TrueNAS server of a friend of mine.

He has created a jail and a dedicated dataset for me, I can see it in the jail, everything looks fine.

But when I use zfs send/zfs receive, I get the following message "cannot receive new filesystem stream: invalid backup stream".

I have spent a lot of time searching the internet and I wonder if the feature large_dnode is not the issue.

From the target jail, I can see that the zpool has this feature inactive/unsupported "unsupported@org.zfsonlinux:large_dnode inactive local". But this feature is enable if I ask my friend to query the pool directly from the TrueNas system "feature@large_dnode enabled local".

We don't want to use TrueNAS replication as it will give me access to all the data of my friend's NAS via SSH. Or we have to spend time to do a setup to avoid that.

Is there a way to solve this issue ? Or I'm totally wrong with this approach ?

Thanks

 

[sretalla]

Is there a way to solve this issue ? Or I'm totally wrong with this approach ?

Not sure, but you might want to think about this:

ZFS - Mount zfs dataset in iocage jail

I can't figure out how to mount an additional ZFS dataset inside an iocage jail. I've created the dataset on the host and did zfs jail (jid) (pool/dataset). The dataset shows up with zfs list inside the jail but zfs mount (pool/dataset) as root returns cannot mount: ... permission denied. The...

forums.freebsd.org

Has anything like that been set on the remote jail?

 

[nico-truenas]

Hi sretalla

yes everything has been setup on the remote jail. I can use zfs create on it without issue

Only the zfs send/receive part is not working

 

[sretalla]

when I use zfs send/zfs receive, I get the following message "cannot receive new filesystem stream: invalid backup stream".

can you share the details of this command you're using? perhaps there's some syntax or logic problem we can help you to correct somehow.

 

[nico-truenas]

This is the command I'm using

zfs send data/nextcloud@autosnap_2021-03-14_18:53:11_daily | ssh -p xxx yyyy "zfs recv all_data/NicoJail/nextcloud"
cannot receive new filesystem stream: invalid backup stream

I have also tried sanoid/syncoid and got the same message

 

[Samuel Tai]

First, what's the value of zpool get feature@large_dnode <name of pool> on both sides? See http://zfs.datto.com/man/man5/zpool-features.5.html.

Then, what's the value of zfs get dnodesize <name of pool>/path/to/nextcloud on both sides?

 

[sretalla]

I may be off track here, but I didn't think you could have colon characters in the name of a snapshot. Can you manually try it with a snapshot that doesn't have any?

 

[nico-truenas]

First, what's the value of zpool get feature@large_dnode <name of pool> on both sides? See http://zfs.datto.com/man/man5/zpool-features.5.html.

Then, what's the value of zfs get dnodesize <name of pool>/path/to/nextcloud on both sides?

Regarding the zpool

• On my TrueNAS

# zpool get feature@large_dnode
NAME PROPERTY VALUE SOURCE
data feature@large_dnode enabled local
freenas-boot feature@large_dnode disabled local

• Inside the jail on the remote TrueNAS

# zpool get feature@large_dnode
#

• On the remote TrueNAS

# zpool get feature@large_dnode
NAME PROPERTY VALUE SOURCE
data feature@large_dnode enabled local

Regarding the zfs

• On my TrueNAS

# zfs get dnodesize data/nextcloud
NAME PROPERTY VALUE SOURCE
data/nextcloud dnodesize legacy default

• On the remote TrueNAS

# zfs get dnodesize all_data/NicoJail
bad property list: invalid property 'dnodesize'

 

[nico-truenas]

I may be off track here, but I didn't think you could have colon characters in the name of a snapshot. Can you manually try it with a snapshot that doesn't have any?

I have tried it and got the same message

 

[sretalla]

Maybe inheritance was somehow (deliberately?) broken on that dataset and it was created before the pool was updated?

Not sure how you manually set a feature on a dataset, but perhaps it can be done... looks like it's just not there on the target.