All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allan Wind <allan_wind@lifeintegrity.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-ide@vger.kernel.org, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: LSISAS1068E + WDC WD2002FYPS: I/O error & Sense Key
Date: Mon, 3 Aug 2009 12:06:29 -0400	[thread overview]
Message-ID: <20090803160629.GA2011@lifeintegrity.com> (raw)
In-Reply-To: <1249310093.3943.11.camel@mulgrave.site>

On 2009-08-03T09:34:53, James Bottomley wrote:
> On Mon, 2009-08-03 at 01:08 -0400, Allan Wind wrote:
> >
> > The above complains about sector 3907028974 which is exactly 
> > 19566 sectors greater than the size of the raid array according 
> > to parted.  In other words it appears to be an access to the last 
> > sector of the array.
> 
> If it's a read beyond the end of a partition, then it's possible it got
> rejected in the partition checking logic before ever reaching the I/O
> controller (which would explain why no messages from the fusion in the
> log).
> 
> However, I don't think the analysis is correct.  Parted says
> 
> 
> > Number  Start   End          Size         File system  Name  Flags
> >  1      34s     19565s       19532s                          bios_grub
> >  2      19566s  3907029134s  3907009569s  ext3               raid
> 
> So the absolute sector number 3907028974 is within partition 2.

I was actually trying to make a different point.  Namely that it 
was curious that the error message complains about sector
3907028974 which is exactly the size of the array + 19566, or in 
other words 1 sector past the end of array:

/dev/sdb2
start: 19566
end: 3907029134
size: 3907029134 - 19566 + 1 = 3907009568

/dev/md0
start: 0
end: 3907009407
size: 3907009407 - 0 + 1 = 3907009408

If dm maps linear to the disk sectors:

dm  /dev/sdb2
0   19566
1   19567
...
3907009406 3907028972
3907009407 3907028973

What dm sector would map to physical sector 3907028974?


/Allan
-- 
Allan Wind
Life Integrity, LLC
<http://lifeintegrity.com>


  reply	other threads:[~2009-08-03 16:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27  6:03 LSISAS1068E + WDC WD2002FYPS: I/O error & Sense Key Allan Wind
2009-07-29 19:43 ` Robert Hancock
2009-07-29 20:07   ` Allan Wind
2009-07-29 23:04     ` Robert Hancock
2009-07-31 18:40       ` Allan Wind
2009-08-03  5:08         ` Allan Wind
2009-08-03 14:34           ` James Bottomley
2009-08-03 16:06             ` Allan Wind [this message]
2009-08-03 16:15               ` James Bottomley
2009-08-26 21:17                 ` Allan Wind
2009-09-11  6:20                   ` Jeppe Oland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090803160629.GA2011@lifeintegrity.com \
    --to=allan_wind@lifeintegrity.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.