Thanks alot Mathias for the pointer.

I've checked out issue #41/42 on linuxcare, and it concludes that there's
no solution found yet for this situation.

For me, this situation started when I upgraded to kernel 2.2.12 and
2.2.13.  No errors before that.

By the way, did I mention that my hard drive was completely wiped out?  I
wonder if any body else experienced that level of severity.

Thanks

robert


On 10 Nov 1999, Matthias Andree wrote:

> Robert Johannes <[EMAIL PROTECTED]> writes:
> 
> > Oct 21 06:09:27 okurut kernel: attempt to access beyond end of device
> > Oct 21 06:09:27 okurut kernel: 08:04: rw=0, want=1819044973,
> > limit=6136830
> > Oct 21 06:09:27 okurut kernel: dev 08:04 blksize=1024 blocknr=1819044972
> > sector=-656877352 size=1024 count=1
> > Oct 21 06:09:27 okurut kernel: attempt to access beyond end of device
> > Oct 21 06:09:27 okurut kernel: 08:04: rw=0, want=1819044973,
> > limit=6136830
> > Oct 21 06:09:27 okurut kernel: dev 08:04 blksize=1024 blocknr=1819044972
> > sector=-656877352 size=1024 count=1  
> > Oct 21 06:09:27 okurut kernel: attempt to access beyond end of device
> > Oct 21 06:09:27 okurut kernel: 08:04: rw=0, want=1819044973,
> > limit=6136830
> 
> That's something about which you can read in Kernel Traffic #41 (check
> http://www.kt.linuxcare.com) 
> 
> > If anybody can enlighten as to why I'm getting total data wipe-outs, and
> > these error messages, please help.  It is a very discomforting thought to
> > realize that these errors might lead to another data wipe-out.
> 
> It seems that "access beyond end of device" will cause major ext2
> corruption. However, I have not fully followed the corresponding threads
> in the linux-kernel ML, I've only read the summary in Kernel
> Traffic. Maybe you should check the linux-kernel archives. 
> 
> -- 
> Matthias Andree
> 
> Hi! I'm the infamous .signature virus!
> Copy me into your ~/.signature to help me spread!
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to