public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Pawan Prakash Sharma <pawanprakash101@gmail.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfs duplicate UUID
Date: Wed, 25 Mar 2020 18:37:37 +0100	[thread overview]
Message-ID: <20200325183737.634580f5@harpe.intellique.com> (raw)
In-Reply-To: <CABS7VHCuGgu0N5ZSXXSKQE9R5ngzAedv_TdZDMt-CHWDfhRZEg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

Le Wed, 25 Mar 2020 20:35:03 +0530
Pawan Prakash Sharma <pawanprakash101@gmail.com> écrivait:

> > Note that even after freezing, the on-disk filesystem can contain  
>  information on files that are still in  the process of unlinking.
>  These files will not be unlinked until the filesystem is unfrozen or
> a clean mount of the snapshot is complete.
> 
> hmmm, ok, so what is the right way to do it?
> Sould mount the cloned volume with nouuid first so that log is
> replayed and filesystem is clean, then umount it and then generated
> the UUID for this using xfs_admin command.
> 

Yes, that looks like the proper way to do it. Zeroing the og with
xfs_repair is usually a last resort thing that you'd rather not do
unless it's unavoidable.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

  parent reply	other threads:[~2020-03-25 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 16:13 xfs duplicate UUID Pawan Prakash Sharma
2020-03-24 16:16 ` Christoph Hellwig
2020-03-24 17:28   ` Emmanuel Florac
2020-03-24 17:38 ` Emmanuel Florac
2020-03-24 17:44   ` Pawan Prakash Sharma
2020-03-24 18:26     ` Emmanuel Florac
     [not found]       ` <CABS7VHDt=v1SmSggnn8288uE5Cs27RqXpPsbiGk9=wyJ-pz1pQ@mail.gmail.com>
2020-03-25 14:24         ` Emmanuel Florac
2020-03-25 16:55           ` Pawan Prakash Sharma
     [not found]           ` <CABS7VHCuGgu0N5ZSXXSKQE9R5ngzAedv_TdZDMt-CHWDfhRZEg@mail.gmail.com>
2020-03-25 17:37             ` Emmanuel Florac [this message]
2020-03-25 20:05               ` Pawan Prakash Sharma

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=20200325183737.634580f5@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pawanprakash101@gmail.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