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] File-system uuid on LVM snapshot
Date: Thu, 05 Jun 2014 12:31:23 +0200	[thread overview]
Message-ID: <539046FB.8090701@redhat.com> (raw)
In-Reply-To: <1021489358.18243958.1401960596909.JavaMail.zimbra@redhat.com>

Dne 5.6.2014 11:29, Rajesh Joseph napsal(a):
> Thanks Zdenek for the quick reply.
>
> We are using thin volumes and thin snapshot, but we need all or most snapshots active. Therefore we are enabling the snapshot by-default.
> As you suggested we can have a workaround to mount those snapshot volumes by using 'nouuid' option.
> But the problem is in most of our use case the origin volume is mounted using the /etc/fstab. And here the mount entry is made using UUID.
> So in some cases instead of Origin volume the snapshot volume get mounted.


So this rather looks like you are not using  'snapshot' as snapshot but rather 
as a quick COW device clone - where you obviously need to change identifiers, 
since they are used later independently. (something like we do with 
'vgimportclone' where we duplicate VG)

Maybe it might be worth to think about fsadm extension to support filesystem 
cloning as a built-in feature which would handle change if fs UUID across 
different filesystems...

Regards

Zdenek

      reply	other threads:[~2014-06-05 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1208338730.18211142.1401956193776.JavaMail.zimbra@redhat.com>
2014-06-05  8:26 ` [linux-lvm] File-system uuid on LVM snapshot Rajesh Joseph
2014-06-05  9:19   ` Zdenek Kabelac
2014-06-05  9:29     ` Rajesh Joseph
2014-06-05 10:31       ` Zdenek Kabelac [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=539046FB.8090701@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).