From: Eric Sandeen <sandeen@sandeen.net>
To: David Brown <davidb@davidb.org>, linux-xfs@vger.kernel.org
Subject: Re: Unable to xfsdump/xfsrestore filesystem
Date: Tue, 3 Mar 2020 10:57:20 -0600 [thread overview]
Message-ID: <fc20f54e-9bfc-4487-af18-c83da9e2bf8b@sandeen.net> (raw)
In-Reply-To: <20200303165000.GA33105@davidb.org>
On 3/3/20 8:50 AM, David Brown wrote:
> I am using xfsdump with multiple levels to backup my main system
> (Fedora f31, xfs root and home on LVM). Kernel is
> 5.5.6-201.fc31.x86_64.
>
> When doing a test restore of my backup, when I reach my level 2
> backup, I get the following warnings:
>
> xfsrestore: directory post-processing
> xfsrestore: WARNING: unable to rename dir orphanage/422178422.2232121414 to dir <<path>>/b-cloud: No such file or directory
>
> In addition, I get hundreds of these. They seem to all be related to
> that same directory.
>
> xfsrestore: restoring non-directory files
> xfsrestore: WARNING: open of orphanage/422178422.2232121414/modules/atmel/cmake_install.cmake failed: No such file or directory: discarding ino 2833282
> xfsrestore: WARNING: open of orphanage/422178422.2232121414/modules/atmel/asf/common/cmake_install.cmake failed: No such file or directory: discarding ino 2833283
>
> When I verify the restore (using https://github.com/d3zd3z/rsure), I
> indeed find that <<path>>/b-cloud is missing, but another directory
> next to it is still present that should be removed.
>
> Restores of subsequent print similar messages (and don't restore the
> directory), until one of them dies with this:
>
> xfsrestore: WARNING: unable to rename dir orphanage/422178422.2232121414 to dir <<path>>/b-cloud: No such file or directory
> xfsrestore: node.c:539: node_map: Assertion `nh != NH_NULL' failed.
>
> Any ideas on how to debug this?
xfsdump/restore is a beast to debug. Are you using the latest version of xfsdump package?
Can you put the entire restore session logs somewhere, possibly with verbosity increased?
(Any chance you have the dump logs, still?)
-Eric
next prev parent reply other threads:[~2020-03-03 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 16:50 Unable to xfsdump/xfsrestore filesystem David Brown
2020-03-03 16:57 ` Eric Sandeen [this message]
2020-03-03 22:18 ` Dave Chinner
2020-03-13 14:43 ` David Brown
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=fc20f54e-9bfc-4487-af18-c83da9e2bf8b@sandeen.net \
--to=sandeen@sandeen.net \
--cc=davidb@davidb.org \
--cc=linux-xfs@vger.kernel.org \
/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