From: "Erick Calder" <e@arix.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] read_intr errors
Date: Wed, 17 Oct 2001 13:08:30 -0700 [thread overview]
Message-ID: <000801c15747$7d86df10$0300000a@pacbell.net> (raw)
In-Reply-To: <20011017152957.E644@tykepenguin.com>
Patrick,
> I'm afraid they look a lot like hardware errors to me. It might just be
that it
> doesn't like MULTI_MODE though. I'm not an IDE expert.
I turned MULTI_MODE on at a suggestion aimed to fix these very problems...
they certainly are hardware errors but as we know anecdotally from other
postings, the hardware can be perfectly ok and the errors still persist. as
my drive is brand new and I had no such errors before installing a PV on it,
it seems reasonable to think it's not the drive.
is my data at risk of corruption? I've slowly been checking the integrity
of files but I'm concerned about backing up bad data!
-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of Patrick Caulfield
Sent: Wednesday, October 17, 2001 7:30 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read_intr errors
On Wed, Oct 17, 2001 at 02:27:21AM -0700, Erick Calder wrote:
> hi everyone, I've read a number of dialogues on the archives concerning
the
> errors below which I'm getting but have not found any answers:
>
> I'm running RedHat 7.0 (2.4.9 kernel + LVM 1.0.1rc1) on a little PIII box
> and I'm using the ide controllers built into the motherboard (drivers
built
> into the kernel - not modules). I have CONFIG_IDEDISK_MULTI_MODE set to y
> in the .config for the kernel. The drive is an IBM-DTLA-307030 (as
reported
> by /proc/ide) and is brand new.
>
> here are the errors:
>
> Oct 17 02:00:34 beowulf kernel: hdc: read_intr: error=0x04 {
> DriveStatusError }
> Oct 17 02:00:34 beowulf kernel: hdc: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Oct 17 02:00:34 beowulf kernel: hdc: read_intr: error=0x04 {
> DriveStatusError }
> Oct 17 02:00:34 beowulf kernel: ide1: reset: success
>
> I've been moving data in and out of the drive and everything seems ok but
I
> get lots of the above errors which leaves me with a queasy feeling...
> anyone know what the deal is with this?
I'm afraid they look a lot like hardware errors to me. It might just be that
it
doesn't like MULTI_MODE though. I'm not an IDE expert.
patrick
_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
next prev parent reply other threads:[~2001-10-17 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 16:19 [linux-lvm] Remount a LVM Vol after a system crash Christoph Berger
2001-10-16 21:40 ` Heinz J . Mauelshagen
2001-10-17 9:27 ` [linux-lvm] read_intr errors Erick Calder
2001-10-17 14:29 ` Patrick Caulfield
2001-10-17 20:08 ` Erick Calder [this message]
2001-10-18 7:42 ` Patrick Caulfield
2001-10-23 23:19 ` Erick Calder
2001-10-24 4:25 ` Patrick Caulfield
2001-10-26 2:13 ` Erick Calder
2001-10-26 3:29 ` Patrick Caulfield
2001-10-26 16:16 ` Erick Calder
2001-10-30 2:55 ` Patrick Caulfield
-- strict thread matches above, loose matches on Subject: below --
2001-10-17 20:21 Karl
2001-10-17 21:20 ` Erick Calder
2001-10-18 0:09 ` Wolfgang Weisselberg
2001-10-17 22:27 Karl
2001-10-24 11:36 Karl
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='000801c15747$7d86df10$0300000a@pacbell.net' \
--to=e@arix.com \
--cc=linux-lvm@sistina.com \
/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;
as well as URLs for NNTP newsgroup(s).