Linux LVM users
 help / color / mirror / Atom feed
From: Matt Schillinger <mschilli@vss.fsi.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] disk naming
Date: Fri Jan  3 10:59:02 2003	[thread overview]
Message-ID: <1041613503.20036.49.camel@mosix> (raw)
In-Reply-To: <20030103174618.Z9539@zealot.blacknet.de>

If i'm NOT using devfs, can i reliably (assuming that disks are on the
same scsi id/lun/host channel) use lvm?

Scenario:

LV is created with device /dev/sdd, which is on host channel 2

Machine is shutdown, and a new raid is connected on host channel 1, with
one disk.

Machine is restarted, and the 1 disk on the host channel 1 raid takes
/dev/sdd. The original disk is now /dev/sde.

Will LVM find the correct disk?

Matt Schillinger
mschilli@vss.fsi.com



On Fri, 2003-01-03 at 10:46, Goetz Bock wrote:
> 
> On Fri, Jan 03 '03 at 10:08, Matt Schillinger wrote:
> > this should be a simple question, but I can't find a direct discussion
> > in the lvm documentation. I believe that i have found that LVM will find
> > appropriate PV's regardless of their name (sda,sdb).. Is this true?
> Kind of. When you created (maybe even just used) a PV/VG with DEVFS it
> will only work with devfs. 
> IIRC when you compile DEVFS into the kernel, but do not mount it, you
> can create PVs, but createvg will not find them unless you mount devfs.
> 
> > Do i need devfs to ensure that i always have the same disk naming, or
> > will LVM handle this for me?
> devfs does not ensure you have the same names.
> 
> > I am currently using scsidev for naming purposes, but have found that
> > vgcreate will not work with scsidev device names
> > (/dev/scsi/sdh0-0c0i4l2p1)
> > /dev/scsi/sd(host=0,scsiid=4,LUN=2,partition #=1)
> Most likely the userspace tools do not search the /dev/scsi/sdxxx
> devices for PV signatrue. IIRC there is one file where you can add them. 
> It's in tools/lib/lvm_check_partitioned_dev.c but I've no idea how to
> add your devices.
> -- 
> Goetz Bock       (c) 2002 as     blacknet.de - Munich - Germany   /"\
> IT Consultant    GNU FDL 1.1    secure mobile Linux everNETting   \ /
>                                                                    X
>  ASCII Ribbon Campaign against HTML email & microsoft attachments / \
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
-- 
Matt Schillinger
System Administrator
FlightSafety International
mschilli@vss.fsi.com
314-551-8403

  reply	other threads:[~2003-01-03 10:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 10:02 [linux-lvm] disk naming Matt Schillinger
2003-01-03 10:45 ` Goetz Bock
2003-01-03 10:59   ` Matt Schillinger [this message]
2003-01-03 11:03     ` Patrick Caulfield
2003-01-03 12:53       ` Matt Schillinger
2003-01-03 13:12         ` Steven Lembark
2003-01-03 12:30     ` Steven Lembark
2003-01-03 13:20       ` Patrick Caulfield
2003-01-04  1:09         ` Steven Lembark
2003-01-04  3:59           ` Patrick Caulfield
2003-01-04 12:27             ` Steven Lembark
2003-01-04 12:40               ` Theo Van Dinter
2003-01-04 13:55               ` Patrick Caulfield
2003-01-08 10:28                 ` Matt Schillinger
2003-01-03 12:21 ` Steven Lembark

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=1041613503.20036.49.camel@mosix \
    --to=mschilli@vss.fsi.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