linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: <ardy@rdb.linux-help.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Slackware init
Date: Mon, 26 Feb 2001 16:39:46 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.20.0102261635050.7246-100000@rdb.linux-help.org> (raw)
In-Reply-To: <20010226082718.B1481@sistina.com>

On Mon, 26 Feb 2001, AJ Lewis wrote:

> I think the issue is that /proc is not yet mounted when you call vgscan.
> If you look at the tools/lib/lvm_dir_cache.c file at line 90, you will
> see that it checks for /proc/partitions.  If it finds that, it only scans
> the files in /proc/partitions.  Otherwise, it goes through all the possible
> devices LVM recognizes. 
> 
> So if you can get /proc mounted before you call vgscan, it should not take
> so long, nor should it scan for all those devices you do not have on your
> system.

Well this is the problem, since I'm trying to mount the volumes from fstab
when mount is called, how would I go about getting /proc mounted after /
is mounted read-write, but before vgscan is run?
Have /proc mounted with a separate command in rc.S after / is remounted rw
and before vgscan is run?

Are there other alternatives, like removing unused emtries in /dev, to cut
down scan time (as was mentioned on this list earlier)?

  parent reply	other threads:[~2001-02-26 21:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-25 18:33 [linux-lvm] Slackware init ardy
2001-02-25 23:52 ` AJ Lewis
2001-02-26 12:08   ` ardy
2001-02-26 14:27     ` AJ Lewis
2001-02-26 17:29       ` Andreas Dilger
2001-02-27  0:14         ` [linux-lvm] FYI Functioning " ardy
2001-02-26 21:39       ` ardy [this message]
2001-02-26 22:15         ` [linux-lvm] " Andreas Dilger
2001-02-26 23:21           ` ardy

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=Pine.LNX.4.20.0102261635050.7246-100000@rdb.linux-help.org \
    --to=ardy@rdb.linux-help.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;
as well as URLs for NNTP newsgroup(s).