All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Corry <kevcorry@us.ibm.com>
To: evms-devel@lists.sourceforge.net
Cc: pierre.machard@idealx.com, Benoit Picaud <benoit@idealx.com>,
	'Mathias BROSSARD' <mbrossard@idealx.com>,
	Alasdair G Kergon <agk@redhat.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [Evms-devel] Re: [linux-lvm] [BUG] Spaces in LVM1 LV names => *deep trouble* when converting to LVM2
Date: Wed, 10 May 2006 16:20:28 -0500	[thread overview]
Message-ID: <200605101620.29326.kevcorry@us.ibm.com> (raw)
In-Reply-To: <20060510203626.GW16180@agk.surrey.redhat.com>

On Wed May 10 2006 3:36 pm, Alasdair G Kergon wrote:
> On Wed, May 10, 2006 at 10:26:14PM +0200, Dominique Quatravaux wrote:
> > Hi, I encountered a very serious bug with LVM today. I'm using
> > lvm2-2.01.04-5 from Debian stable, kernel 2.6.17-rc3
> > # lvm version
> >   LVM version:     2.01.04 (2005-02-09)
> >   Library version: 1.01.00-ioctl (2005-01-17)
> >   Driver version:  4.6.0
> > What I did:
> >     * created a LV in an LVM1 VG using EVMS (yeah, I know) with a
> >       space in the name (yeah, yeah, I know, I know :-));
>
> LVs are not permitted to have spaces in their names.
> EVMS should have prevented you from doing that!

Hmm...looks like the lvm2 format plugin in EVMS does check for spaces when 
creating a new VG or LV, but the lvm1 format plugin does not. I've added a 
patch to fix the lvm1 plugin. Sorry for the trouble. :(  I guess this case is 
sufficiently unusual that no one has hit before, or at least not mentioned it 
to me before.

-- 
Kevin Corry
kevcorry@us.ibm.com
http://www.ibm.com/linux/
http://evms.sourceforge.net/

      parent reply	other threads:[~2006-05-10 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 20:26 [linux-lvm] [BUG] Spaces in LVM1 LV names => *deep trouble* when converting to LVM2 Dominique Quatravaux
2006-05-10 20:36 ` Alasdair G Kergon
2006-05-10 20:40   ` Alasdair G Kergon
2006-05-11  7:55     ` Dominique Quatravaux
2006-05-10 21:20   ` Kevin Corry [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=200605101620.29326.kevcorry@us.ibm.com \
    --to=kevcorry@us.ibm.com \
    --cc=agk@redhat.com \
    --cc=benoit@idealx.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=linux-lvm@redhat.com \
    --cc=mbrossard@idealx.com \
    --cc=pierre.machard@idealx.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.