From: Stewart Smith <stewart@linux.org.au>
To: Jeremy Salch <salch@tblx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Access past end of device
Date: Thu, 5 Jun 2003 04:40:08 +1000 [thread overview]
Message-ID: <20030604184008.GB9732@cancer> (raw)
In-Reply-To: <002001c32abe$10a18700$9fdeae3f@TBLXM>
On Wed, Jun 04, 2003 at 12:23:50PM -0500, Jeremy Salch wrote:
> I did a fdisk on the device /dev/sda and it found no bad blocks.
That's a good thing - be greatful :)
> I was given the suggestion from one person it sounds like a kernel bug since
> redhat patches their kernels soo much.
Could be, try a kernel.org kernel and see if the problem persists. If it goes away, file a bug report with redhat. I would think fdisk would come up with an error on a corrupt partition map, so if it doesn't then ur probably looking at some oddity... try the kernel.org kernel :)
- stew
prev parent reply other threads:[~2003-06-04 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 16:13 Jeremy Salch
2003-06-04 17:02 ` Stewart Smith
2003-06-04 17:14 ` Jeremy Salch
2003-06-04 17:23 ` Jeremy Salch
2003-06-04 18:40 ` Stewart Smith [this message]
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=20030604184008.GB9732@cancer \
--to=stewart@linux.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=salch@tblx.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®