From: Ryan Murray <rmurray@cyberhqz.com>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] bug in liblvm 0.7 [added on 11/15/1998]
Date: Tue, 10 Aug 1999 22:59:55 -0700 [thread overview]
Message-ID: <19990810225955.A14275@cyberhqz.com> (raw)
In-Reply-To: <199908020957.AA21641@mailgate1b.telekom.de>; from Heinz Mauelshagen on Mon, Aug 02, 1999 at 11:57:11AM +0000
On Mon, Aug 02, 1999 at 11:57:11AM +0000, Heinz Mauelshagen wrote:
> the simple idea behind this was to avoid not neccessary accesses in case of
> a regular /dev layout (no trouble in case of devfs anyway).
"regular" seems to vary from distribution to distribution,
unfortunately.
> If we put to much effort into holding up this concept i'ld rather say
> "let's throw it away and open all existing device special nodes in turn".
That may be the best bet. Although it would be nice if it was smart
enough to throw away what it's already done. If /dev/hda doesn't exist,
don't do any /dev/hda's. And if /dev/hda is a full LVM drive, you may
as well not check partitions. At this point, it's caused more problems
than majorly noted speed improvements, for me.
For now, I've created fifteen md and loop devices, even though I use 0. I
suppose I could just remove them all...
>
> Any opinions?
It's either got to be ripped out, or made *really* smart. At this
point, I think it's why vgscan is failing. Which brings me to my next
point, it would be nice if vgscan would say something on partial volume
groups, ie: "only 9/20 drives found for volume group "vg00", leaving
offline"
I think this code is what caused vgscan to fail for me. Going to try it
now that I've added all the device files...
--
Ryan Murray (rmurray@cyberhqz.com, rmurray@glenayre.com)
Software Designer, Glenayre Technologies Inc.
The opinions expressed here are my own.
prev parent reply other threads:[~1999-08-11 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-31 20:58 [linux-lvm] bug in liblvm 0.7 [added on 11/15/1998] Ryan Murray
1999-08-02 9:57 ` Heinz Mauelshagen
1999-08-11 5:59 ` Ryan Murray [this message]
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=19990810225955.A14275@cyberhqz.com \
--to=rmurray@cyberhqz.com \
--cc=linux-lvm@msede.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.