linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read_intr errors
Date: Wed Oct 24 04:25:02 2001	[thread overview]
Message-ID: <20011024101331.A2271@tykepenguin.com> (raw)
In-Reply-To: <003001c15c42$f7faa4c0$0300000a@pacbell.net>; from e@arix.com on Tue, Oct 23, 2001 at 09:18:44PM -0700

On Tue, Oct 23, 2001 at 09:18:44PM -0700, Erick Calder wrote:
> Patrick,
> 
> sorry for the delay, it takes 12 hours to back up this guy and another 12 to
> verify... and I had problems so I had to do it several times.
> 
> so if I get you correctly, I should be able to do badblock check (instead of
> a mke2fs with -c option as has been suggested) and get an evaluation for
> whether this drive has problems equally well, no?
> 
> here's what I did:
> 
> # df -k
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/hda1             38456308   2670876  33831932   8% /
> /dev/LVM/mp3z         29540436  13308716  14731152  48% /var/mp3z
> 
> # umount /dev/LVM/mp3z
> # vgchange -a n
> vgchange -- volume group "LVM" successfully deactivated
> 
> root@beowulf:/root # badblocks -s /dev/hdc 29540436
> Checking for bad blocks (read-only test): done

Well that looks OK
 
> as you can see, no errors.  Now, having said that, I've come to realise that
> the errors I get happen when accessing my tape drive (which is scsi) - at
> least I think that's what's happening... weird.  do you then think this is
> related to the problems others have had? and if so, was there a fix?

The thread about SCSI errors just stopped so I don't know what happened there.
There was some thought that maybe LVM was trying to access beyond the end of the
disk so you could check to see if the LV is using all the space on /dev/hdc and
back it off a little so see if that helps. It may also be worth upgrading to
LVM 1.0.1rc4.

If it is the SCSI tape drive interfering then that's really odd because SCSI
shouldnot interfere with IDE unles you have some interrupt clashes or perhaps
bad cabling causing signal noise.

Not very conclusive I'm afraid, but I did say I wasn't an IDE expert!

patrick

  reply	other threads:[~2001-10-24  4:25 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
2001-10-18  7:42         ` Patrick Caulfield
2001-10-23 23:19           ` Erick Calder
2001-10-24  4:25             ` Patrick Caulfield [this message]
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=20011024101331.A2271@tykepenguin.com \
    --to=caulfield@sistina.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).