Rogério Brito <[email protected]> wrote:
> On Sep 28 2005, Nigel Cunningham wrote:
>> 3) Is the corruption only ever in memory, or seen on disk too?
>
> I have noticed the problem mostly on disk. One strange situation was
> when I was untarring a kernel tree (compressed with bzip2) and in the
> middle of the extraction, bzip2 complained that the thing was
> corrupted.
>
> I removed what was extracted right away and tried again to extract the
> tree (at this point, suspecting even that something in software had
> problems). The problem with bzip2 occurred again. Then, I rebooted the
> system an the problem magically went away.
I have a similar problem:
It's a corruption while reading data from the HDD into the cache.
The affected page will contain (pseudo?)random data in the first four
bytes (at least on my system it did).
If you waited long enough, the cache page would be discarded and the next
read from the disk would be correct. However, if it happens e.g. in an
inode block, the corruption may find it's way to the disk and/or fubar
your data.
This happens mostly if there are concurrent DMA transfers like playing
sound or watching TV on bttv cards. I'm affected by the later cause,
setting no_overlay reduced it.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
