From: Eric Sandeen <sandeen@sandeen.net>
To: L A Walsh <xfs@tlinx.org>, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfsdump | xfsrestore resulting in files->orphanage
Date: Wed, 24 Mar 2021 18:58:47 -0500 [thread overview]
Message-ID: <529ae732-9525-4152-3399-290c38355026@sandeen.net> (raw)
In-Reply-To: <605BB7AA.4050500@tlinx.org>
On 3/24/21 5:05 PM, L A Walsh wrote:
> copying a disk to a replacing disk I am using
> xfsdump on the fromdir and xfsrestore on the todir.
>
> I finish another disk a short while ago with no probs, but this
> disk starts out with a weird message from xfsdump:
>
>
> xfsdump: NOTE: root ino 192 differs from mount dir ino 256, bind mount?
>
> Then later, when it starts restoring files on the target,
> all the files end up in the orphanage:
>
> xfsrestore: 9278 directories and 99376 entries processed
> xfsrestore: directory post-processing
> xfsrestore: restoring non-directory files
> xfsrestore: NOTE: ino 709 salvaging file, placing in orphanage/256.0/Library/Music/ Maria/Cover-Inside.jpg
> xfsrestore: NOTE: ino 710 salvaging file, placing in orphanage/256.0/Library/Music/ Maria/Cover-Outside.jpg
>
> The files look "fine" on the source
> Never had a simply "copy" go so wrong...
>
> What might be causing this?
This is a bug in root inode detection that Gao has fixed, and I really
need to merge.
In the short term, you might try an older xfsdump version, 3.1.6 or earlier.
(Assuming you don't actually have a bind mount)
Sorry about that.
-Eric
next prev parent reply other threads:[~2021-03-24 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 22:05 xfsdump | xfsrestore resulting in files->orphanage L A Walsh
2021-03-24 23:58 ` Eric Sandeen [this message]
2021-03-25 0:43 L A Walsh
2021-03-25 1:16 ` Gao Xiang
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=529ae732-9525-4152-3399-290c38355026@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@vger.kernel.org \
--cc=xfs@tlinx.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;
as well as URLs for NNTP newsgroup(s).