All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Joseph <rjoseph@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] File-system uuid on LVM snapshot
Date: Thu, 5 Jun 2014 05:29:56 -0400 (EDT)	[thread overview]
Message-ID: <1021489358.18243958.1401960596909.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <53903637.5030800@redhat.com>

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.

Thanks & Regards,
Rajesh

----- Original Message -----
> From: "Zdenek Kabelac" <zkabelac@redhat.com>
> To: linux-lvm@redhat.com
> Sent: Thursday, June 5, 2014 2:49:51 PM
> Subject: Re: [linux-lvm] File-system uuid on LVM snapshot
> 
> Dne 5.6.2014 10:26, Rajesh Joseph napsal(a):
> > Hi all,
> >
> > Origin volume and snapshot volume share the same file-system UUID. So after
> > the snapshot we fix the uuid by running xfs_admin or tune2fs.
> > Do you have any recommendation or best practice in this regard?
> >
> 
> 
> With thin pools and thin volumes - snapshot of thin volume is now created
> 'inactive' and it's skipped from default activation  (you could always
> override skip with -K  i.e. : lvchange -ay -K vg/mythinsnap)
> 
> So with thins you should mostly have only a single volume active with the FS
> UUID.  If you happen to have multiple volumes active and you need to mount
> xfs
> filesystem  - use  'nouuid' (and eventually  norecovery for read-only
> activated snapshots)  mount options.
> 
> For old-snapshosts - all volumes need to be available/active - so you need to
> use 'nouuid' option always.
> 
> I don't see much point in changing  FS UUID on your snapshot - unless of
> course you plan to use snapshots as different volumes with just a 'single'
> starting point  (i.e. preinstalled tree of files)
> 
> Regards
> 
> Zdenek
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

  reply	other threads:[~2014-06-05  9:29 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 [this message]
2014-06-05 10:31       ` 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=1021489358.18243958.1401960596909.JavaMail.zimbra@redhat.com \
    --to=rjoseph@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 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.