[SOLVED] Can't cp: Read error: Value too large for defined data type

dtjohnst · 2017-10-05 05:12:43

Hello everyone,

I'm trying to backup some files that are sitting on an old NTFS hard drive, and I'm trying to copy them to a samba share (ext4 on the server). The file is only 11MiB in size, but all I can find in Google is talk about how my "core utils were compiled without support for large files". Having said that, large files seems to me mutli-GiB files which obviously isn't the case. For that matter, larger files cp with no problem.

I've tried copying to a local ext4 partition as well instead of to a samba share. I was skeptical given that it says "read error", but tried anyway and of course it failed with the same error. I tried with rsync as well. This is error from attempting a local copy, but the messages are identical when trying to copy to the samba share.

# cp /mnt/local/Travel/2015/Trip\ 1\ -\ Scandinavia/Scandinavia\ \(Fall\ 2015\)\ -\ 1234.NEF ~/
cp: error reading '/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF': Value too large for defined data type

# rsync /mnt/local/Travel/2015/Trip\ 1\ -\ Scandinavia/Scandinavia\ \(Fall\ 2015\)\ -\ 1234.NEF ~/
rsync: read errors mapping "/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF": Value too large for defined data type (75)
rsync: read errors mapping "/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF": Value too large for defined data type (75)
ERROR: Scandinavia (Fall 2015) - 1234.NEF failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2]

I have no idea what to do about this.

Last edited by dtjohnst (2017-10-05 16:30:39)

ewaller · 2017-10-05 14:49:28

Let's try another operation on that file.

What happens if you try sha256sum /mnt/local/Travel/2015/Trip\ 1\ -\ Scandinavia/Scandinavia\ \(Fall\ 2015\)\ -\ 1234.NEF

Also, that is a hideous file name. You might try changing its name to something sans spaces and parentheses.

dtjohnst · 2017-10-05 15:48:33

ewaller wrote:

Let's try another operation on that file.
What happens if you try sha256sum /mnt/local/Travel/2015/Trip\ 1\ -\ Scandinavia/Scandinavia\ \(Fall\ 2015\)\ -\ 1234.NEF
Also, that is a hideous file name. You might try changing its name to something sans spaces and parentheses.

I'm hoping to once it's moved and solidly on Linux footing but in windows that was a perfectly acceptable filename.

# sha256sum /mnt/local/Travel/2015/Trip\ 1\ -\ Scandinavia/Scandinavia\ \(Fall\ 2015\)\ -\ 1234.NEF
sha256sum: '/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF': Value too large for defined data type

V1del · 2017-10-05 15:54:36

What driver are you using to acess that drive? Maybe the kernel ntfs keels over for whatever reason, maybe some metadata mismatch when trying to read file info out of the NTFS metadata or similar. Try with https://wiki.archlinux.org/index.php/NTFS-3G

ewaller · 2017-10-05 15:55:59

The sha256sum command should read every sector of the file while creating a hash. It does this without copying or moving anything.
So, either there is a problem with the file structure, a bad sector, or the name is causing issues.

Try this one: sha256sum "/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF"

Edit: I second V1del's suggestion

Last edited by ewaller (2017-10-05 15:57:36)

seth · 2017-10-05 16:03:05

dd if='/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF' of=~/somejunkfile

How exactly do you mount NTFS? (ntfs or ntfs-3g)
Can you boot windows and perform a filesystem check? - Simply renaming the file might actually do.
(I'd rather trust windows than the linux ntfs implementions here)

The error is most likely in the metadata of the file (name/attributes) and not the file itself.

Edit: shit. again.

Last edited by seth (2017-10-05 16:03:54)

dtjohnst · 2017-10-05 16:03:09

V1del wrote:

What driver are you using to acess that drive? Maybe the kernel ntfs keels over for whatever reason, maybe some metadata mismatch when trying to read file info out of the NTFS metadata or similar. Try with https://wiki.archlinux.org/index.php/NTFS-3G

I have tried both the baked-in Kernel drivers and ntfs-3g and get the same error messages. Sorry, should have mentioned that in my initial post.

dtjohnst · 2017-10-05 16:06:20

seth wrote:

dd if='/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF' of=~/somejunkfile
How exactly do you mount NTFS? (ntfs or ntfs-3g)
Can you boot windows and perform a filesystem check? - Simply renaming the file might actually do.
(I'd rather trust windows than the linux ntfs implementions here)
The error is most likely in the metadata of the file (name/attributes) and not the file itself.
Edit: shit. again.

dd "works" after spitting out an error, but the file is corrupt. I will try it on windows when I get a chance and report back.

# dd if=/mnt/local/Travel/2015/Trip\ 1\ -\ Scandinavia/Scandinavia\ \(Fall\ 2015\)\ -\ 1234.NEF of=~/somejunkfile.NEF
dd: error reading '/mnt/local/Travel/2015/Trip 1 - Scandinavia/Scandinavia (Fall 2015) - 1234.NEF': Value too large for defined data type
21608+0 records in
21608+0 records out
11063296 bytes (11 MB, 11 MiB) copied, 3.96085 s, 2.8 MB/s

EDIT: Should clarify that it's corrupt as in I can't open it with any suitable software that I have (lightroom, photoshop, etc). For all I know this problem exists with the original file too and is causing the error. We'll see if Windows has the same problem.

Last edited by dtjohnst (2017-10-05 16:10:58)

dtjohnst · 2017-10-05 16:30:24

Managed to get it to work.

Before either removing the HDD from the machine and putting it in a windows one or making a Win10 PE LiveUSB, I just installed samba and set up a share. Over on a windows machine I accessed the share and tried to copy the file: failed. I then opened the file in Windows 10 Photo Viewer, which worked fine. So I just saved a copy from Windows Photo viewer, transferred that back to the share, and it copies, rsyncs and sha256sums just fine. Seems quite odd, but problem solved all the same. Thanks everyone.

Last edited by dtjohnst (2017-10-05 16:31:07)

Arch Linux

#1 2017-10-05 05:12:43

[SOLVED] Can't cp: Read error: Value too large for defined data type

#2 2017-10-05 14:49:28

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#3 2017-10-05 15:48:33

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#4 2017-10-05 15:54:36

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#5 2017-10-05 15:55:59

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#6 2017-10-05 16:03:05

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#7 2017-10-05 16:03:09

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#8 2017-10-05 16:06:20

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

#9 2017-10-05 16:30:24

Re: [SOLVED] Can't cp: Read error: Value too large for defined data type

Board footer