Johan,
Thanks for sending the bulk information about this bug. I have never seen the buffer
bug
when running local loads, only when using nfs. The bug appears more often when running
with 64MB of RAM or less, but has been seen when using more memory.
Below is a sample of the errors seen while doing tests. Very interesting is that the
same
buffer had a problem within 5 minutes with all having different buffers.
These all look like potential data corruption since multiple buffers are assigned to
the
same physical block. I have seen corruption, but the corruption seems to be because of
the nfs client, not the server side.
Hopefully, this problem will get resolved soon, but it looks like it has been with us
for
some time now (2 years.)
<>< Lance.
Mar 1 22:33:10 src@lance-v raid5: bug: stripe->bh_new[2], sector 26272 exists
Mar 1 22:33:10 src@lance-v raid5: bh c100b680, bh_new c0594bc0
Mar 1 22:37:32 src@lance-v raid5: bug: stripe->bh_new[2], sector 26272 exists
Mar 1 22:37:32 src@lance-v raid5: bh c2d1be60, bh_new c1edcea0
Mar 1 22:42:41 src@lance-v raid5: bug: stripe->bh_new[3], sector 360880 exists
Mar 1 22:42:41 src@lance-v raid5: bh c1777840, bh_new c1777780
Mar 2 03:26:37 src@lance-v raid5: bug: stripe->bh_new[2], sector 1792 exists
Mar 2 03:26:37 src@lance-v raid5: bh c0549240, bh_new c0ed30c0
Mar 2 09:07:38 src@lance-v raid5: bug: stripe->bh_new[0], sector 293016 exists
Mar 2 09:07:38 src@lance-v raid5: bh c20150c0, bh_new c2015600
Mar 2 14:10:08 src@lance-v raid5: bug: stripe->bh_new[2], sector 42904 exists
Mar 2 14:10:08 src@lance-v raid5: bh c084c5c0, bh_new c262b8a0
