zfs send.rec from Freenas 9.10.2-U6 to TrueNAS-13.0-U1.1 - is that safe operation?

[phier]

@Samuel Tai thanks for your effort.

i executed rsync with -c ; ie checksum md5 and it finished without error ... i assume in that case i can be 100% sure data was securely transferred?

appreciate.

 

[Samuel Tai]

Yes, that's pretty definitive.

 

[phier]

@Samuel Tai
hello, seems there are 2 major issues;

1) rsync finished with errors ;
some of them are like that

Code:

filename overflows max-path len by 3: hdcubox/usb/root/old_data/sdcard/usr/lib/python2.7/encodings/cp875.pyc/root/.cache/pip/http/f/e/d/0/e/fed0ed508030b766d5b0c2792132c8bf197804464765b46b361f93a4.lock/d/6/4/5/1d64584e92602feb17a86d9818a6020c216c9a04bcf58fb91c2f5a13.lock/8/1/5/f/b815fa1f94838c81257ce7fc81c211030faed8ae929786addd8e5e6d.lock/a/3/a6da33837c55be9a1a6a6d3dcf3b9d954ca08015113dd2881751b75c.lock/8/6/1/18861927018e48868814409e45a13145ab9a3378b805d94eb3cd7445.lock/9/6/c/7196c3ff908b7a10387eac35b18dd50ee540c161355304e892e999d8.lock/7/6/7/2/d767226ed021b50d876a25956965493020198191aa5b80c1e57417a6.lock/1/9/2/1f192afbf07ab233717470233964bfec58f1cf9c70e1b632cdab062d.lock/2/f/5/0/62f501feea8d35db6a568fd7c46a72949138b3f5e7ee7165ba22063b.lock/a/6/1/b2a617c86469a4b248e09c6e8ac693b3ce48b936ec01ff92fa5fcd4e.lock/c/1/7/1/3c171901426c0b70b38195354f7c8dfef64334ecb8bf28375ce03f42.lock/c/0/f/d8c0fbdd6ee08381faa7902d0eac122e040fb425604ffd022d0f7b26.lock/e/7/b/a1e7b24174197d2f5eb6474931f0836468b6f2a0765f20d1e2cefee7.lock/17d3c6760f52b42b487b872a6c576a26c3a951

other issues i cant see - bc rsync is not generating error log :(


2) if i do rsync on mountpoint lets say /mnt/media and under media dataset are other datasets like /mnt/media/video; /mnt/media/music
the files from sub-datasets video ; music are not copied via rsync

any idea? thanks!

 

[Samuel Tai]

With respect to recursive traversals of daughter datasets, rsync has never had that ability. You’ll need to set the rsyncs for those yourself.

As for the path length errors, don’t nest datasets too deeply. Also make sure your pool and dataset names don’t have any spaces.

 

[phier]

@Samuel Tai ah okay, i thought as ls can see files there same will apply for rsync

regarding the path length errors;
original dataset structure is

problematic data are stored in storage3 dataset;

i try to copy them here>

so basically source is
/mnt/storage3

target: (where storage3 is directory)
/mnt/universalsoldier/freenas/storage3

so will it help if i move it from universalsoldier/freenas just to
/mnt/universalsoldier/storage3
(where storage3 is directory)

thanks

 

[phier]

@Samuel Tai hi not sure, but we are talking about ~20gb not mb difference.

[root@freenas] /mnt# du -s -g storage4/
6247 storage4/

truenas
du -s -g storage4/
6267 storage4/


so 20gb on metadata is possible? thanks

when i use mc to calculate total size in MiB results are same... so seems issue in du command?

 

[Samuel Tai]

du is known not to grok ZFS very well. It's better to look at the figures from zfs get usedbydataset <name of dataset>, zfs get usedbysnapshots <name of dataset>, zfs get usedbychildren <name of dataset>, and zfs get usedbyrefreservation <name of dataset>.

 

[phier]

@Samuel Tai thanks, assuming on file level ie not on dataset there is no tool to do the space measurement ... bc i needed to calculate size on directory not dataset level.

thx