Christoph Anton Mitterer wrote:
Roger Heflin wrote:
The failure can manifest itself in many ways, I have
only seen it as a read failure, but there should be no
reason why it cannot also show as a write failure.
It should be in the later vanilla kernels, it won't
be in the earlier ones, I would do a
find /lib/modules -name "*edac*" -ls
It is a hw issue, either something is running faster that
it should be (pci bus set to fast for the given hardware/config)
or something is broken.
The strange thing is that it always occures on the copied data,.. not
the original (which is on another disk). But wouldn those parity errors
not occur in general?
For example al my sha1sums -c sumfile checks are working corretly on the
original disk :/
Are both disks of the same type and connected to the same
hardware?
Or do they have different physical connections/drivers to the
machine?
Roger
-
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]
