From: Oliver Rath <rath@mglug.de>
To: lvm-devel@redhat.com
Subject: thinpool-block-device exists twice after renaming
Date: Tue, 27 Aug 2013 15:03:05 +0200 [thread overview]
Message-ID: <521CA389.504@mglug.de> (raw)
Hi list,
Im using here lvm2 (2.02.99) with Ubuntu 12.04 wiht LTS-Kernel-Stack
(3.8er Kernel).
I ecreated a volume group an in this volume group a thinpool. Then i
created thinpool devices from this pool. So far, so fine
The thinpool devices are links in /dev/myvg/tp-device-1 ->
/dev/mapper/myvg-tp-device-1.
These were also links to /dev/dm-X devices.
NOW i rename a tp-device. The result is en error "cannot rename ..", BUT
in /dev/myvg/ the links are renamed and pointing - which looks strange
to me - to block-devices in /dev/mapper/ instead of links.
These block-devices have the same maior/minor-ids at hte /dev/dm-X
devices, so now the renamed block-device exists twice.
Any ideas to solve this?
Regards
Oliver
next reply other threads:[~2013-08-27 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 13:03 Oliver Rath [this message]
2013-08-27 13:32 ` example [was Re: thinpool-block-device exists twice after renaming] Oliver Rath
2013-08-27 13:43 ` Zdenek Kabelac
2013-08-27 14:13 ` Oliver Rath
2013-08-27 14:17 ` lvm.conf " Oliver Rath
2013-08-27 13:35 ` example " Oliver Rath
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=521CA389.504@mglug.de \
--to=rath@mglug.de \
--cc=lvm-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.