linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: "Linda A. Walsh" <lvm@tlinx.org>
Subject: Re: [linux-lvm] dmsetup -split is buggy
Date: Mon, 15 Aug 2011 13:30:34 +0200	[thread overview]
Message-ID: <4E49035A.9090202@redhat.com> (raw)
In-Reply-To: <4E48E81C.9040504@tlinx.org>

On 08/15/2011 11:34 AM +0100, Linda A. Walsh wrote:
> dmsetup splitname, should, I believe, know how to split
> names in the only 'supported' name format  i.e. /dev/VG/LV -- but
> instead, it's treating it as though it were under /dev/mapper and using that for
> decoding...

dmsetup splitname accepts a device-mapper name as an argument,
/dev/VG/LV is a "logical volume path" and is not supposed to be
decoded this way...

Peter

      parent reply	other threads:[~2011-08-15 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  9:34 [linux-lvm] dmsetup -split is buggy Linda A. Walsh
2011-08-15 10:09 ` Stephane Chazelas
2011-08-15 11:30 ` Peter Rajnoha [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=4E49035A.9090202@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=lvm@tlinx.org \
    /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).