All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S. J. van Harmelen" <svh@dds.nl>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Use LVM on /dev/mapper/diskname and iSCSI
Date: Mon, 19 Nov 2007 16:07:27 +0100	[thread overview]
Message-ID: <1195484847.6074.16.camel@sanderbal> (raw)
In-Reply-To: <47419854.2000508@linpro.no>

Thanks for your help!

I executed the pvs command and it did find a few partitions. I use iSCSI
to share the LUN's to a XenSource server, and XenSource creates the PV's
and LV's in order to provision VM's. Didn't think of that, but that's on
the disk of course. 

Is there any way to configure snapshots for these already created LVM
partitions? Or do I have to whipe the disk clean (rather not do that,
but if I have to it can be done), then create the pv's and lv's and then
share the lv's true iSCSI?

In that case XenSource will again create pv's and lv's in the shared lv.
Ain't that a problem?

Sander



On Mon, 2007-11-19 at 15:06 +0100, Tore Anderson wrote:
> * S. J. van Harmelen
> 
> > I have a couple of LUN's that are handled by the multipath driver.
> > This works great, but now I want to use LVM so I can take snapshots
> > of one LUN to another LUN.
> > 
> > Can someone tell me how to do this?
> > 
> > When I do pvcreate /dev/mapper/diskname I get an error that the disk
> > is already part of an volume group. But I sertainly did not configure
> > that.
> > 
> > Can it be that the multipath driver of devmapper did that?
> 
> If you have a PV signature on the volume, LVM might have used one of the
> paths instead of using the multipath'ed device under /dev/mapper.  You
> should be able to check this by running the command "pvs" - it should
> list all the detected PVs on your system.
> 
> If this was the problem, you can avoid it by instructing LVM to not scan
> SCSI devices directly, by adding a line in /etc/lvm/lvm.conf like this:
> 
> device {
>   filter = [ "a|^/dev/mapper/.*|", "r|.*|" ]
> }
> 
> This will make LVM only look at devices in /dev/mapper/ as possible PV
> candidates, ignoring all other devices.  Beware if you have a PV on the
> internal drives though, you might want to have something like this
> instead in that case (if that PV is on /dev/sda2, for instance):
> 
>   filter = [ "a|^/dev/mapper/.*|", "a|^/dev/sda2$|", "r|.*|" ]
> 
> Make sure lvm.conf makes its way into the initramfs if you start the LVM
> stuff there.  I know Ubuntu doesn't include this file by default, at least.
> 
> Regards

  reply	other threads:[~2007-11-19 15:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 13:56 Use LVM on /dev/mapper/diskname S. J. van Harmelen
2007-11-19 14:06 ` Tore Anderson
2007-11-19 15:07   ` S. J. van Harmelen [this message]
2007-11-19 18:43     ` Use LVM on /dev/mapper/diskname and iSCSI Tore Anderson
2007-11-19 21:19       ` S. J. van Harmelen
2007-11-20 14:14         ` Chip Coldwell
2007-11-20 14:22           ` S. J. van Harmelen
2007-11-19 18:50     ` malahal
2007-11-19 21:16       ` S. J. van Harmelen
2007-11-19 22:36         ` malahal
2007-11-20  9:38           ` S. J. van Harmelen
2007-11-20  7:36         ` Tore Anderson
2007-11-20  9:36           ` S. J. van Harmelen
2007-11-20  9:49             ` Tore Anderson
2007-11-20 10:10               ` Possible bug in multipathd (getting a segfault) S. J. van Harmelen
2007-11-20 10:21                 ` Tore Anderson
2007-11-20 10:34                   ` S. J. van Harmelen
2007-11-20 11:15                     ` Tore Anderson
2007-11-20 11:25                       ` S. J. van Harmelen
2007-11-20 11:28                       ` S. J. van Harmelen
2007-11-26 20:40                       ` S. J. van Harmelen
2007-11-19 16:57   ` Use LVM on /dev/mapper/diskname and iSCSI S. J. van Harmelen
2007-11-19 17:22   ` Use LVM on /dev/mapper/diskname malahal
2007-11-19 18:13     ` S. J. van Harmelen
2007-11-19 18:16     ` S. J. van Harmelen

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=1195484847.6074.16.camel@sanderbal \
    --to=svh@dds.nl \
    --cc=dm-devel@redhat.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.