From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM seems to be causing SCSI errors.
Date: Mon, 8 Oct 2001 17:20:39 +0100 [thread overview]
Message-ID: <20011008172039.A4196@btconnect.com> (raw)
In-Reply-To: <135135307.1002326338570.JavaMail.root@boots>; from rmvzj001@sneakemail.com on Fri, Oct 05, 2001 at 07:52:50PM -0000
On Fri, Oct 05, 2001 at 07:52:50PM -0000, Karl wrote:
> > Well, if it is within the size of the drive, and you get a "bad noise"
> > when trying to access it, then it may be that you have a bad drive. If
> > you are doing low-level formats of the drive, this may do bad block
> > relocation, and hide the fact that there are bad spots.
>
> That's what I thought at first, but as I explained earlier, the errors
> ONLY occur when running under LVM and go away as soon as I use the raw
> disk. I went back and forth several times. I'm pretty sure it is an LVM
> thing, but no idea what it is.
The only thing I can think is that the SCSI device is not being
opened/initialised properly by LVM. This certainly wasn't happening
before ~July when I put the open/close_pv() functions in. But should
be working now. Puzzled. You really are using the new tools and not
old binaries in strange places ? I've been caught a couple of times
by this ...
- Joe
next prev parent reply other threads:[~2001-10-08 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 19:52 [linux-lvm] LVM seems to be causing SCSI errors Karl
2001-10-08 10:10 ` Heinz J . Mauelshagen
2001-10-08 16:20 ` Joe Thornber [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 16:57 Karl
2001-10-09 13:55 Karl
2001-10-09 15:12 ` Joe Thornber
2001-10-08 17:37 Karl
2001-10-08 10:51 Karl
2001-10-09 9:21 ` Heinz J . Mauelshagen
2001-10-08 10:46 Karl
2001-10-05 18:21 Karl
2001-10-05 22:58 ` Andreas Dilger
2001-10-05 16:58 Karl
2001-10-05 21:31 ` Andreas Dilger
2001-10-08 10:07 ` Heinz J . Mauelshagen
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=20011008172039.A4196@btconnect.com \
--to=thornber@btconnect.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).