Thanks for the follow up - as I mentioned in the follow up, I have made the
problem go away by using the default chunk size for raid10.
As this is my main file server I don't really want to recreate the problem.
If I get a spare afternoon I'll perhaps try to recreate the bug on a less
critical mach
Following the above, I did this:
1) stop nfs server daemon, unmount /home, stop /dev/md4
2) make a new md4 with default chunk size (64KiB) but otherwise the same as
above
3) made a new xfs filesystem on md4 using md3 as log device, as before
4) mount this as /home, export via nfs
5) restore 1.2TB
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/651846/+attachment/1656524/+files/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/651846/+attachment/1656525/+files/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
Public bug reported:
Binary package hint: linux-image-2.6.32-25-preempt
Asus p5q premium intel motherboard has 6 identical discs on the ICH10
controller, configured mostly as a raid10 array, with an xfs filesystem mounted
on /home and exported via nfs.
Errors are consistently seen writing large
