From mboxrd@z Thu Jan  1 00:00:00 1970
From: Oleg Drokin <green@namesys.com>
Subject: Re: Error message - vs-13070
Date: Mon, 17 Feb 2003 16:41:26 +0300
Message-ID: <20030217164126.A11276@namesys.com>
References: <5.2.0.9.0.20030215000534.018ed008@mail.bogus.home> <5.2.0.9.0.20030215000534.018ed008@mail.bogus.home> <5.2.0.9.0.20030216203350.018dd7d8@mail.bogus.home> <20030216153359.GA28622@mrball.net> <20030217091552.A20096@namesys.com> <3E50E549.8060307@namesys.com>
Mime-Version: 1.0
Return-path: <reiserfs-list-return-12789-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
Content-Disposition: inline
In-Reply-To: <3E50E549.8060307@namesys.com>
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com

Hello!

On Mon, Feb 17, 2003 at 04:36:09PM +0300, Hans Reiser wrote:
> >>>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >>>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6599945, 
> >>>sector=4286584
> >>>end_request: I/O error, dev 03:03 (hda), sector 4286584
> >>>These errors look to me like a hardware problem (bad sector on the 
> >>>drive).
> >>>Definately not a reiserfs problem, thanks for the reply Oleg.
> >>Depends, is 4286584 beyond the end of what really exists, or is that in
> >>the middle of your valid sectors?
> >Reads/writes beyond end of device emit different messages.
> how about defining that in our faq.

Defining of what?
Q: What does "attempt to access beyond end of device" messages mean?
A: This means that there was attempt to read outside of device.

I see no point in such entries at all.

Bye,
    Oleg