linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Karl" <rmvzj001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LVM seems to be causing SCSI errors.
Date: 05 Oct 2001 16:58:15 -0000	[thread overview]
Message-ID: <135641898.1002315768965.JavaMail.root@boots> (raw)

This is a real odd problem and my searching of the mailing lists and
docs has not shed any light on it.

I created 3 logical volumes (with lvm 1.0.1r2, r3 and r4) across 4 disks
on a dual 300 MHz PII running 2.4.6 (same behavior under 2.4.9) and
readhat 7.1. After this I noticed IO errors while reading some files
and SCSI errors when accessing lvol2. The errors were similar to the
following


Sep 28 17:11:21 gar kernel: scsi0: ERROR on channel 0, id 11, lun 0, CDB: Read (10) 00 00 ba e1 97 00 00 80 00 
Sep 28 17:11:21 gar kernel: Info fld=0xbae1e6, Current sd08:21: sense key Medium Error
Sep 28 17:11:21 gar kernel: Additional sense indicates Unrecovered read error
Sep 28 17:11:21 gar kernel:  I/O error: dev 08:21, sector 12247456


lvol2 spanned two disks and all the errors were on only one of them. I
naturally thought that the problem was a hardware problem with the
disk. The only odd thing was that lvol1 which spanned the same two disks
did not have any errors.

The first thing I tried was an mke2fs with bad block checking on
lvol2. It found several errors and when I copied the files back on new
errors cropped up and more files were lost.

The next thing I did was to move all the data off of that disk (pvmove)
and then did a low level format on that disk. No errors were detected
during the low lever format nor the verify I did after that. I then did
a mke2fs with bad block checking on the disk without LVM. No errors. I
then did a pvcreate and re-created lvol2 and then did a mke2fs with bad
block checking. Once again the SCSI errors. Removing that drive from LVM
and formatting yet again without LVM showed no errors.

Moving lvol2 to a different physical volume results in the SCSI errors
moving to that volume.

I am now convinced that the problem is with LVM and not with the
hardware. I still have two other logical volumes (lvol1 and lvol3) that
are not having ANY problems at all. Does anyone have any suggestion on
how to solve this one?

Thanks.


-----------------------------------------------------
Protect yourself from spam, use http://sneakemail.com

             reply	other threads:[~2001-10-05 16:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 16:58 Karl [this message]
2001-10-05 21:31 ` [linux-lvm] LVM seems to be causing SCSI errors Andreas Dilger
2001-10-08 10:07 ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2001-10-05 18:21 Karl
2001-10-05 22:58 ` Andreas Dilger
2001-10-05 19:52 Karl
2001-10-08 10:10 ` Heinz J . Mauelshagen
2001-10-08 16:20 ` Joe Thornber
2001-10-08 10:46 Karl
2001-10-08 10:51 Karl
2001-10-09  9:21 ` Heinz J . Mauelshagen
2001-10-08 17:37 Karl
2001-10-09 13:55 Karl
2001-10-09 15:12 ` Joe Thornber
2001-10-09 16:57 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=135641898.1002315768965.JavaMail.root@boots \
    --to=rmvzj001@sneakemail.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).