1352 NUL bytes at the end of a page?
We've got a user who's reporting BK problems which we've traced down to the fact that his s.ChangeSet file has a hole, filled with '\0' bytes, that's so far always 1352 bytes long, and the end is page-aligned. (In fact, the two cases we've seen so far have been 8k-aligned.) The correct file data picks up again after the hole.
bk is writing the data using stdio in a child process (fork, exec, wait), then mmaping the result. The corruption is persistent; he sent us the s.ChangeSet file and there it was (not a cache or buffering problem, therefore).
2.6.6-bk (current head of tree from whenever he built), UP PIII, symptom observed on both ext3 and reiserfs. (However, we've explicitly verified the hole only on reiser.)
The problem is intermittent, having happened "several" times over the last few months, and doesn't appear to be tied to any particular kernel version.
To me, this looks awfully close to an Ethernet frame size... but that's just a wild guess. And I don't think he's running Ethernet (still waiting for dmesg and .config).
I've asked for more info, memtest86, and will attempt to reproduce it on another box.
Does anyone have insight into this peculiar problem?
-andy
Quoted 6 lines · Andy Isaacson
We've got a user who's reporting BK problems which we've traced down to the fact that his s.ChangeSet file has a hole, filled with '\0' bytes, that's so far always 1352 bytes long, and the end is page-aligned. (In fact, the two cases we've seen so far have been 8k-aligned.) The correct file data picks up again after the hole.
When the reporter has a PIII machine it's often useful to find out the clock frequency - the lower it is, the older it is and the more likely it is that some component has rotted.
If this one cannot be reproduced on any other machine I'd say it's a hardware failure.