Re: access beyond end of device errors in 2.2.13pre18 AND 2.2.5
P.A.M. van Dam (nucleus@ramoth.xs4all.nl)
Thu, 28 Oct 1999 17:52:49 +0200
On Thu, Oct 28, 1999 at 12:54:01PM +0100, Stephen C. Tweedie wrote:
> Hi,
>
> On 28 Oct 1999 12:13:01 +0200, Martin Schulz
> <schulz@iwrmm.math.uni-karlsruhe.de> said:
>
> > May be. My box in question runs knfsd (1.2.2-4). But the error message
> > (=symptom) occurs on local operation. And the corruption goes much
> > beyond that message if not fsck'ed soon. (Been there, done that.)
>
> 1.2.2-4?? That is ancient, and there was a bug in knfsd's rmdir
> operation which could cause exactly these symptoms. Please upgrade to
> knfsd-1.4.7 and see if you can reprodce the problem.
>
> We know that (a) dodgy hardware and (b) the knfsd problem can explain
> huge numbers of these reports, but it's hard to completely exclude the
> possibility of other faults in the current kernels. It would really
> help to eliminate variables if you could go to a more recent knfsd.
As replied earlier, I'm not using NFS (knfsd) and experience the "beyond
end of device" messages while doing extensive IO on a 4-way striped LV.
A single LV gives no problem.
My setup is an NCR875 with 2x4Gb,2x8Gb and 2Gb for the rootdisk.
A kernel compile on this LV, a database fill on both oracle or Sybase will
all trigger the bug.
Hope this helps a little.
Best regards,
Pascal
>
> --Stephen
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/