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>,
	xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfs duplicate UUID
Date: Wed, 25 Mar 2020 15:24:36 +0100	[thread overview]
Message-ID: <20200325152418.04340a72@harpe.intellique.com> (raw)
In-Reply-To: <CABS7VHDt=v1SmSggnn8288uE5Cs27RqXpPsbiGk9=wyJ-pz1pQ@mail.gmail.com>

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

Le Tue, 24 Mar 2020 23:58:24 +0530
Pawan Prakash Sharma <pawanprakash101@gmail.com> écrivait:

> >Your problem is that the log is dirty. You need to mount it once to  
> clean up the log, then you'll be able to change the UUID.
> 
> But why xfs_freeze is not clearing that as man page says that it does
> that?

Please reply to the list so that anyone interested can learn about it. 

This is mentioned in the man page at the next line:

 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.

You probably have open unlinked files (such as temporary files). It's
very common.

-- 
------------------------------------------------------------------------
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 14:24 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 [this message]
2020-03-25 16:55           ` Pawan Prakash Sharma
     [not found]           ` <CABS7VHCuGgu0N5ZSXXSKQE9R5ngzAedv_TdZDMt-CHWDfhRZEg@mail.gmail.com>
2020-03-25 17:37             ` Emmanuel Florac
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=20200325152418.04340a72@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