read: Value too large for defined data type

[epitron]

'fatrace' is a great little program, but it seems to have trouble with large files (> 2gigs).

If I try to access one of these files while 'fatrace' is running, it prints "read: Value too large for defined data type", and terminates.

I'm currently looking for a solution.

[epitron (chris-ill-logic)]

Turns out, this is a bug in the kernel.

This patch fixes it: https://patchwork.kernel.org/patch/2142341/

But, as of linux v3.8.4, it still hasn't been included.

[epitron (chris-ill-logic)]

So, I've filed this bug in a few places, and it's still unresolved.

The Linux kernel is ignoring the patch. The fanotify API says that you should be able to specify O_LARGEFILE when you use fanotify_init (in the last comment): https://bugs.archlinux.org/task/34520

I've read that putting "#define _LARGEFILE_SOURCE / #define _FILE_OFFSET_BITS 64" at the top of your .c file should enable largefile support, but I think that only works within that one C file. The error is happening inside the fanotify kernel module, which is what's actually opening the file.

[Martin Pitt (pitti)]

Fixed in trunk r54.

[Martin Pitt (pitti)]

Fixed in new upstream release: https://launchpad.net/fatrace/trunk/0.7

[Launchpad Janitor (janitor)]

This bug was fixed in the package fatrace - 0.7-1

---------------
fatrace (0.7-1) unstable; urgency=medium

  * New upstream release:
    - Use O_LARGEFILE to fix "Value too large for defined data type" error
      with large files on some platforms. (LP: #1161989, Closes: #722901)
    - Increase buffer size to 256 KiB. (LP: #1312095)

 -- Martin Pitt <email address hidden> Thu, 07 Aug 2014 09:41:25 +0200

[Martin Pitt (pitti)]

For the record, while this helped a bit it's still not fully functional. See bug 1372873.