From: "Karl" <rmvzj001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read_intr errors
Date: Wed Oct 24 11:36:02 2001 [thread overview]
Message-ID: <134687340.1003941444401.JavaMail.root@boots> (raw)
> 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.
I have not had a chance to try the last suggestion of seeing if I have
problems on an MD device. There has not yet been a solution to the SCSI based
problems.
--
Karl Hakimian
XXXXXXXXXXXXXXXX
next reply other threads:[~2001-10-24 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 11:36 Karl [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-17 22:27 [linux-lvm] read_intr errors Karl
2001-10-17 20:21 Karl
2001-10-17 21:20 ` Erick Calder
2001-10-18 0:09 ` Wolfgang Weisselberg
2001-10-16 21:40 [linux-lvm] Remount a LVM Vol after a system crash 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
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
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=134687340.1003941444401.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.