From: Jos Visser <josv@osp.nl>
To: James Pattinson <jamesp@aethos.co.uk>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] devfs...
Date: Fri, 07 Jan 2000 00:24:40 +0100 [thread overview]
Message-ID: <38752438.EB555FCA@osp.nl> (raw)
In-Reply-To: Pine.LNX.4.10.10001052326530.1271-100000@fuse.aethos.co.uk
Hi,
Maybe I'm a bit silly, but can't vgscan recusively descend into the /dev
directory and try to followup on all block devices it sees there with
exception to the obvious to-be-left-outs?
++Jos
James Pattinson wrote:
>
> OK I've been looking around - and it seems that the latest devfs doesn't
> have /dev/sd/* - instead we have lots of weird things, like
> /dev/discs/disc0/* /dev/discs/disc1/* etc ... I've fixed my vgscan but
> adding
>
> static char *devdir[] = {
> "/dev/ida",
> "/dev/ide/hd",
> "/dev/loop",
> "/dev/md",
> "/dev/rd",
> "/dev/sd",
> + "/dev/discs/disc0",
> + "/dev/discs/disc1",
> + "/dev/discs/disc2",
> + "/dev/discs/disc3",
> + "/dev/discs/disc4",
> "/dev",
> NULL
>
> to lvm_dir_cache.c and similar to pv_check_name.c.
>
> It works for me but hopefully devfs will settle down and not keep changing
> soon...
>
> Thanks,
>
> james
>
> On Wed, 5 Jan 2000, Heinz Mauelshagen wrote:
>
> > > Hi
> > >
> > > I'm sure this is a FAQ but I can't find the answer anywhere.
> > >
> > > I've am using LVM 0.8i on 2.2.14 with the latest devfs patch.
> >
> > Sorry, this combination is not yet supported.
> > I still have to focus on devfs support 8*(
> >
> > > My root
> > > filesystem in on an LV and I have an initrd that does a vgscan and a
> > > vgchange. However now I'm using devfs, vgscan dooesn't find any of my
> > > volume groups - maybe because vgscan doesn't know to look in /dev/scsi or
> > > whatever. Is there a patch to fix this?
> >
> > vgscan (respectively the library routines involved) already
> > take care of devfs naming conventions.
> >
> > Did you mount devfs in linuxrc before running vgscan?
> >
> > Regards,
> > Heinz
> >
> > --
> >
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > Systemmanagement CS-TS T-Nova
> > Entwicklungszentrum Darmstadt
> > Heinz Mauelshagen Otto-Roehm-Strasse 71c
> > Senior Systems Engineer Postfach 10 05 41
> > 64205 Darmstadt
> > mge@EZ-Darmstadt.Telekom.de Germany
> > +49 6151 886-425
> > FAX-386
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
--
"If anyone wants to be first, he must be the very last, and the servant
of all"
next prev parent reply other threads:[~2000-01-06 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-05 17:33 [linux-lvm] devfs James Pattinson
2000-01-05 22:34 ` Heinz Mauelshagen
2000-01-05 23:03 ` James Pattinson
2000-01-05 23:30 ` James Pattinson
2000-01-06 23:24 ` Jos Visser [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-13 20:17 Russell Coker
2000-12-14 15:41 ` Luca Berra
2000-12-14 15:53 ` Christoph Hellwig
2000-12-18 3:36 ` Matthew O'Keefe
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=38752438.EB555FCA@osp.nl \
--to=josv@osp.nl \
--cc=jamesp@aethos.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox