Crashes immediately after start with "read: Value too large for defined data type"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fatrace |
Fix Released
|
Medium
|
Martin Pitt | ||
fatrace (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt |
Bug Description
On my system, after starting fatrace, it spits out a few lines of output and then it crashes in less than a second. Example output:
$ sudo ./fatrace -t
18:26:15.660882 apache2(20446): W /home/user/
18:26:15.677832 mysqld(13748): R /var/lib/
18:26:15.900233 apache2(20177): RO /home/user/
18:26:15.900423 apache2(20177): C /home/user/
18:26:15.900502 apache2(20177): RO /home/user/
18:26:15.900570 apache2(20177): C /home/user/
18:26:15.900617 apache2(20177): O /home/user/
read: Value too large for defined data type
This happens with fatrace 0.7 compiled from LP source tarball on a debian 7.6 machine:
Linux someserver 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
I tested it on four other machines with the same OS, arch and kernel and was not able to reproduce this bug.
Let me know if you need any more information.
Changed in fatrace: | |
status: | New → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Undecided → Medium |
So this is ultimately a kernel bug, which was fixed a few months ago: http:// git.kernel. org/cgit/ linux/kernel/ git/torvalds/ linux.git/ commit/ ?id=1e2ee49f7f1 b79f0b14884fe6a 602f0411b39552
Your test machine runs 3.2, so this definitively doesn't have this fix yet.
A workaround for older kernels is to use the "real" value of O_LARGEFILE (usually it's 0 on amd64, as it's already enabled by default).