linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] libdm cannot swap names between two child volumes
Date: Mon, 08 Jun 2015 09:17:57 +0200	[thread overview]
Message-ID: <557541A5.8050808@redhat.com> (raw)
In-Reply-To: <CAAYit8Q9f+u0FFjR9h6ssUUpZwxwnV5k1rbYeUATMaDn0Un35g@mail.gmail.com>

Dne 8.6.2015 v 04:09 M.H. Tsai napsal(a):
> 2015-06-05 16:04 GMT+08:00 Zdenek Kabelac <zkabelac@redhat.com>:
>> The problem with rename is -
>>
>> you have device   'lv1'  you rename it to 'lv2' - yet
>> those who opened device with the name 'lv1' still thinks
>> the 'lv1' device exits.
>>
>> So for safety reason before you 'reuse' any existing name in-use,
>> there should be 'deactivating' such device first - so there is no 'race' in
>> name usage.
>>
>> It's even possible we miss to track full history of active renamed device.
>>
>> Since you get into strange scenarios when you start to count
>> with udev event handling and link generating here - it's getting nearly
>> impossible to synchronize this properly...
>
> Does that mean, if I can confirm that there's no program using the device name,

Hi

It doesn't really matter here what you could confirm here - there is a race 
you can't avoid - i.e. udev is completely 'independent' and may execute
trigger udev rules at any random point in time or some other command may try 
to open device in parallel (i.e. 'dd')

So the only way how to ensure there is no such race - is to deactivate such 
device (which should be possible - since as you said - noone has it open)

Also remember - activation routine is 'separate' from command code - as it 
could run on a completely different node - so you cannot 'validate' from 
command code there is no user of a device on 'activation' node unless device 
is locally active.

> then it's safe to rename an active device? The devices I want to rename are
> internal volumes. I think that there's no user space program using these names,
> except LVM.

IMHO there is no point to 'optimize' this process - I do not expect anyone is 
doing million swaps of internal LVs in a second.

Thus going through the proper sequence of steps and allowing udev to properly 
synchronize (i.e. you should not 'mix'  activation & deactivation under same 
cookie) is clearly the best way how to achieve your desired goal.

Regards

Zdenek

  reply	other threads:[~2015-06-08  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 10:02 [linux-lvm] libdm cannot swap names between two child volumes M.H. Tsai
2015-06-04 12:14 ` Zdenek Kabelac
2015-06-05  3:32   ` M.H. Tsai
2015-06-05  8:04     ` Zdenek Kabelac
2015-06-08  2:09       ` M.H. Tsai
2015-06-08  7:17         ` Zdenek Kabelac [this message]
2015-06-11  2:54           ` M.H. Tsai
2015-06-11  7:46             ` Zdenek Kabelac

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=557541A5.8050808@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@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).