From: Bradley Alexander <storm@tux.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Can someone _please_ tell me whats going on?
Date: Tue Dec 18 13:07:01 2001 [thread overview]
Message-ID: <1008700601.785.25.camel@defiant> (raw)
In-Reply-To: <Pine.LNX.4.33.0112180820400.22382-100000@dragon.inside.ntisys.com>
I'm going to respond to both of these in the same post.
On Tue, 2001-12-18 at 08:22, Benjamin Scott wrote:
> On 17 Dec 2001, Bradley Alexander wrote:
> > Swapped controllers (was originally on the first controller with the
> > other drive, now on the second.)
>
> FYI, both IDE ports on the motherboard use the same IDE controller chip,
> so if it *is* the controller that is your problem (and given that your disk
> activity light is stuck on, that may be), that will not fix it.
This is true, however, I now have (unlike at the point of my first
attempt to set this up) a vg on the first drive that is working
perfectly. I have seen no problems with it. The problems are only
occurring on the second drive. Also, for the record, I have created a
standard Linux partition via fdisk, made a reiserfs partition, and it is
happily schlepping data without hint of error or problem.
On Tue, 2001-12-18 at 08:50, Lewis Bergman wrote:
>
> Seems strange since so many of us have not had any problems with LVM.
> Have you looked at the kernel notes for any clues to your particular
> hardware? You may find that some controllers/drives/PIO modes do not
> work together. Further tuning with hdparam may alleviate the problem.
> As for myself. I wouldn't put much that is important on a Quantum as
> the quality seems to be fading. I have gone to IBM exclusively. Prices
> are good and I don't know of any better drive out there for ide or
> scsi.
The thing is that the drives are identical (and as I said, vg00 on
/dev/hda is operating without error), so if I was seeing problems, it
should stand to reason that I would see them on both drives.
I am looking at the kernel trap that LVM has been generating. It is
trapping on the vgchange process. I'm limping my way through it with
help.
--
--Brad
============================================================================
Bradley M. Alexander, CISSP | Co-Chairman,
Beowulf System Admin/Security Specialist | NoVALUG/DCLUG Security SIG
Debian/GNU Linux Developer | storm [at] debian.org
| storm [at] tux.org
============================================================================
Why are cigarettes sold at gas stations when smoking is prohibited?
next prev parent reply other threads:[~2001-12-18 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 20:56 [linux-lvm] Can someone _please_ tell me whats going on? Bradley Alexander
2001-12-16 21:11 ` Friedrich Lobenstock
2001-12-16 21:41 ` Bradley Alexander
2001-12-17 1:22 ` Bradley Alexander
2001-12-17 2:41 ` Wolfgang Weisselberg
2001-12-17 6:18 ` Friedrich Lobenstock
2001-12-17 11:36 ` Bradley Alexander
2001-12-17 21:56 ` Bradley Alexander
2001-12-18 7:12 ` Benjamin Scott
2001-12-18 7:50 ` Lewis Bergman
2001-12-18 13:07 ` Bradley Alexander [this message]
2001-12-16 21:44 ` Steven Lembark
2001-12-17 7:11 ` Bradley Alexander
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=1008700601.785.25.camel@defiant \
--to=storm@tux.org \
--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