Skip to contentSkip to conversation

read_intr errors

linux-lvm Karl 3 participants 3 messages Oct 17, 2001 – Oct 18, 2001

lore
Share & tools
lore

Karl

author
#0 lore raw

Have you tried mke2fs with the -c option in LVM and on the drive without LVM? I'm seeing a lot of errors on a SCSI disk that has no hardware problems unless it is in LVM.

Quoted 31 lines · On Wed, Oct 17, 2001 at 02:27:21AM -0700, Erick Calder [email protected]…

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?

1k thx - e

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Signature · 2 lines
Karl Hakimian
XXXXXXXXXXXXXXXX
#1 lore raw

I haven't tried that but if I unmount the filesystem and check it:

# umount /dev/LVM/mp3z
# fsck /dev/LVM/mp3z

it comes up clean.... is that not an equivalent test?

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Karl
Sent: Wednesday, October 17, 2001 1:22 PM
To: [email protected]
Subject: Re: [linux-lvm] read_intr errors

Have you tried mke2fs with the -c option in LVM and on the drive without LVM? I'm seeing a lot of errors on a SCSI disk that has no hardware problems unless it is in LVM.

Quoted 1 line · On Wed, Oct 17, 2001 at 02:27:21AM -0700, Erick Calder [email protected]…

hi everyone, I've read a number of dialogues on the archives concerning

the

Quoted 4 lines

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

Quoted 2 lines

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

Quoted 12 lines

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
Quoted 1 line

I've been moving data in and out of the drive and everything seems ok but

I

Quoted 11 lines

get lots of the above errors which leaves me with a queasy feeling... anyone know what the deal is with this?

1k thx - e

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

--
Karl Hakimian
XXXXXXXXXXXXXXXX

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

#2 lore raw

Hi, Erick!

Quoted 10 lines · Erick Calder

From Karl

Quoted 1 line

Have you tried mke2fs with the -c option in LVM and on the drive without

I haven't tried that but if I unmount the filesystem and check it:

# umount /dev/LVM/mp3z
# fsck /dev/LVM/mp3z

it comes up clean.... is that not an equivalent test?

No. Definitively not. mke2fs -c also runs badblocks(8), which tries to read every single byte in the partition. (Optionally you can even have it do a write test. There is even a non-destructive write test in newer badblocks. Use with care and do have current backups.)

fsck just checks that the metadata (directories, space used by files, etc) looks OK.

-Wolfgang