All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy Salch" <salch@tblx.net>
To: "'Stewart Smith'" <stewart@linux.org.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Access past end of device
Date: Wed, 4 Jun 2003 12:23:50 -0500	[thread overview]
Message-ID: <002001c32abe$10a18700$9fdeae3f@TBLXM> (raw)
In-Reply-To: <20030604170215.GA9732@cancer>

I did a fdisk on the device /dev/sda  and it found no bad blocks.  

I was given the suggestion from one person it sounds like a kernel bug since
redhat patches their kernels soo much.


-----Original Message-----
From: Stewart Smith [mailto:stewart@linux.org.au] 
Sent: Wednesday, June 04, 2003 12:02 PM
To: Jeremy Salch
Cc: linux-kernel@vger.kernel.org
Subject: Re: Access past end of device


On Wed, Jun 04, 2003 at 11:13:02AM -0500, Jeremy Salch wrote:
> I'm using a dell powerall web 120 with scsi drives installed Using 
> redhat 7.2 with the 2.4.18-19.7.x kernel installed
> 
> Attempt to access beyond end of device
> 08:06: rw=0, want=1044196, limit=1044193
> 1044192
> Pass completed, 1 bad blocks found.
> And fdisk reports there to be 1044193+ blocks in the partition ?

Sounds like the partition map is a bit incorrect.

Try running badblocks on the drive itself (/dev/hda, not hda1). If the
problem disappears then it's with the partition map (i'd guess).

- stew


  parent reply	other threads:[~2003-06-04 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 16:13 Access past end of device Jeremy Salch
2003-06-04 17:02 ` Stewart Smith
2003-06-04 17:14   ` Jeremy Salch
2003-06-04 17:23   ` Jeremy Salch [this message]
2003-06-04 18:40     ` Stewart Smith

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='002001c32abe$10a18700$9fdeae3f@TBLXM' \
    --to=salch@tblx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stewart@linux.org.au \
    /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.