68 years to copy a 13 byte file

[BRIT]

I've recently created a backup of a system using Redo 1.0.4 (the latest, I believe). Everything went extremely well (as usual) and as a matter of course, I take the files that were created and place them onto my FreeNAS system (9.10.2 -U6). Today I needed to burn a DVD of those files and so thought the best approach would be to copy the files back onto my local system and then burn the DVD directly from there, rather than having the DVD software have to access the files across a network. The files (as listed on the FreeNAS system) are as follows:

Code:

-rwxr-xr-x 1 dave root		 19 Oct 10 15:46 jeti-3150.backup
-rwxr-xr-x 1 dave root	 32768 Oct 10 15:46 jeti-3150.mbr
-rwxr-xr-x 1 dave root 654208276 Oct 10 15:48 jeti-3150_part1.000
-rwxr-xr-x 1 dave root	8969828 Oct 10 15:50 jeti-3150_part2.000
-rwxr-xr-x 1 dave root	 421624 Oct 10 15:50 jeti-3150_part3.000
-rwxr-xr-x 1 dave root 2147483648 Oct 10 16:02 jeti-3150_part4.000
-rwxr-xr-x 1 dave root 1721116602 Oct 10 16:15 jeti-3150_part4.001
-rwxr-xr-x 1 dave root		250 Oct 10 15:46 jeti-3150.sfdisk
-rwxr-xr-x 1 dave root		 13 Oct 10 15:46 jeti-3150.size

I'm able to copy back from the FreeNAS system all files with the exception of the .size file, that massively huge 13 byte file (apologies for the sarcasm) that I'm being told is only going to take (approximately) 596,523 hours. Yes, that's 68 years...



I obviously have something wrong, but there's nothing in the logs that shows that I have any issues with my disks, or my system at all. FreeNAS 9.10 has been remarkably reliable for me and I actively promote it to others in my technical space. The only entries in /var/log/messages are

Code:

Oct 11 08:57:48 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name				
Oct 11 08:57:48 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name			
Oct 11 09:58:14 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s system-product-name				
Oct 11 09:58:14 freenas alert.py: [common.pipesubr:66] Popen()ing: /usr/local/sbin/dmidecode -s baseboard-product-name			

My workstation is an Ubuntu 18 system.

My config is as follows:

• FreeNAS 9.10.2-U6
• 4 x 3TB drives configured in a zpool
• 16GB RAM
• Sharing via NFS and SMB

Kind of at a bit of a loss what to do here. I find it hard to believe that it's got anything to do with the file itself and there's obviously something going on with FreeNAS but I'm not sure where to start looking ...

 

[joeschmuck]

You could copy the file to another name on FreeNAS and then try to copy that file over and rename it on the destination system. The command would be something like cp jeti-3150.size jeti-3150.bak and if the file is created then try to copy it to your destination location and rename it. If you cannot get the file to copy via the cp command then I'd run a scrub on the pool and try again after it's complete, I don't expect the scrub to fix it but just to rule out any other issues.