From: Phillip Susi <psusi@ubuntu.com>
To: Zdenek Kabelac <zkabelac@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] libdevmapper's handling of devices with spaces in the name
Date: Wed, 26 Feb 2014 15:52:44 -0500 [thread overview]
Message-ID: <530E541C.9040001@ubuntu.com> (raw)
In-Reply-To: <530E3CAA.1070308@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/26/2014 2:12 PM, Zdenek Kabelac wrote:
> As said - there is no bug in libdm - libdm expects udev to create
> nodes. You can reconfigure libdm to do this job instead of udev -
> but then nothing else will work with it - so it's basically
> dead-road...
It doesn't matter who creates it, what matters is that when parted
asks what the correct name is, that it be told the name that actually
is created.
> The best you can do is to not use names which needs mangling -
> that's my best suggestions (and lvm team already spend countless
> hours on some usable workarounds and solutions...)
Unfortunately, it seems that a number of hardware vendors ship
preconfigured fakeraid setups with a space in the name of the volume.
> For mangling see 'dmsetup mangle' help - how to obtain device
> names...
Is there a libdevmapper call to do this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTDlQcAAoJEI5FoCIzSKrw3Z8H/3pS3uLG9vcQOrVba4KMxjN6
PY1uPGCWIUyqiGUYxzyleyAXp7TVyNpvomPEuevToSaEQBjL60jBUW1NNSiqPmsz
Dk9DDGzF7ecmQ3p4w6jPn0+RBKNvLU1jZygxCsMW3A9c2iqhuICkKD+MMDzjj2bw
Af/M6fT8aJBUWCeLeT+egKY2vVHP59j0AyNwj2ei4pBZ+Y2gOoecJTB+kZB7VgJ+
MoY8VdQaQGhMKQLtmmkD5kIDbe7x8f1mYj4y1BUhzvnemu4vpFn7s5wOE41+9cTk
F5J0GWE6OgNQ3oXLktpkt50hQH72rAOOrnlzEpx/SobH6l1oEtB0XpJdyVuiIAc=
=kiNS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-26 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 17:04 [linux-lvm] libdevmapper's handling of devices with spaces in the name Phillip Susi
2014-02-26 18:21 ` Zdenek Kabelac
2014-02-26 18:37 ` Phillip Susi
2014-02-26 19:12 ` Zdenek Kabelac
2014-02-26 20:52 ` Phillip Susi [this message]
2014-02-26 21:40 ` Zdenek Kabelac
2014-02-26 22:17 ` Phillip Susi
2014-02-26 23:26 ` Alasdair G Kergon
2014-02-27 8:51 ` Peter Rajnoha
2014-02-27 9:08 ` Peter Rajnoha
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=530E541C.9040001@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-lvm@redhat.com \
--cc=zkabelac@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 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).