From: Gionatan Danti <g.danti@assyoma.it>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org, g.danti@assyoma.it
Subject: Re: xfs_metadump as a backup tool
Date: Tue, 22 Aug 2017 08:11:46 +0200 [thread overview]
Message-ID: <78a3bcf1cac9fbf47c809cc03a48640b@assyoma.it> (raw)
In-Reply-To: <be09cfb0-39ab-9645-468b-79d6a81aaec8@sandeen.net>
Il 21-08-2017 22:11 Eric Sandeen ha scritto:
> Short answer is "No," because:
> xfs_metadump is only a diagnostic tool. It is not tested or supported
> for any other use.
>
> If nothing else, on a normal live filesystem your metadata and data is
> constantly changing; if you replay old metadata over a filesystem,
> you'll end up pointing to file data blocks that are incorrect.
>
> If you really truly have only statically-allocated files from start to
> finish, then maybe...
>
> But more than anything else, the tool was not designed or tested for
> anything other than developer diagnostics.
>
> For disaster recovery, having periodic metadata snapshots might come
> in handy from a forensic POV, but I would not rely on this as a
> primary part of your normal backup/recovery scheme.
Hi Eric,
thank for your reply. From xfs_metadump man page is read that the tool
should be only used as a debugging aid, but hey - maybe someone used it
in more clever ways ;)
> If you've already done a proper backup wit tar/rsync/(xfsdump?) then
> you have everything you need to restore the filesystem without
> resorting to xfs_metadump cleverness, right?
Sure, but restoring metadata on a corrupted, but healty, volume would be
much faster than restoring both data and metadata. As a first-stop
recovery, maybe it was worth a try. But if nobody is doing that, it
should not be a good idea...
> No, it's not possible to preallocate space on xfs without marking it
> as unwritten.
Understood.
Thanks Eric.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
prev parent reply other threads:[~2017-08-22 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 19:59 xfs_metadump as a backup tool Gionatan Danti
2017-08-21 20:11 ` Eric Sandeen
2017-08-22 6:11 ` Gionatan Danti
2017-08-22 6:11 ` Gionatan Danti [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=78a3bcf1cac9fbf47c809cc03a48640b@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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