From: L A Walsh <xfs@tlinx.org>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: xfsrestore'ing from file backups don't restore...why not?
Date: Mon, 25 Oct 2021 14:30:08 -0700 [thread overview]
Message-ID: <617721E0.5000009@tlinx.org> (raw)
I'm trying to do a cumulative restore a directory
from a multi-file backup w/names:
-rw-rw-r-- 1 1578485336160 Oct 1 06:51 home-211001-0-0437.dump
-rw-rw-r-- 1 262411348256 Oct 23 04:53 home-211023-1-0431.dump
-rw-rw-r-- 1 1881207032 Oct 25 04:31 home-211025-2-0430.dump
At first I tried "-i" but once I got a prompt, no files or directories
were visible.
So I tried restoring the full thing:
I'm getting 1000's of messages like where it doesn't seem to be able
to restore the file and instead places it in the orphanage:
xfsrestore: NOTE: ino 1879669758 salvaging file, placing in orphanage/256.0/tools/libboost/boost_1_64_0/doc/html/boost/accumulators/extract/coherent_tail_mean.html
xfsrestore: NOTE: ino 1879669759 salvaging file, placing in orphanage/256.0/tools/libboost/boost_1_64_0/doc/html/boost/accumulators/extract/count.html
xfsrestore: NOTE: ino 1879669760 salvaging file, placing in orphanage/256.0/tools/libboost/boost_1_64_0/doc/html/boost/accumulators/extract/covariance.html
xfsrestore: NOTE: ino 1879669761 salvaging file, placing in orphanage/256.0/tools/libboost/boost_1_64_0/doc/html/boost/accumulators/extract/density.html
xfsrestore: NOTE: ino 1879669762 salvaging file, placing in orphanage/256.0/tools/libboost/boost_1_64_0/doc/html/boost/accumulators/extract/extended_p_square.html
-----
I've seen this before and was able to restore the file I wanted from
the "orphanage" -- instead of installing into the directory
I gave, it gives the above messages.
xfsdump+restore claim to be from xfsdump-3.1.8-1.3.x86_64
from openSUSE with Build Date : Tue Jan 29 16:46:13 2019
I have also tried this on an empty partition -- same thing.
Why am I not able to restore my backups?
next reply other threads:[~2021-10-25 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 21:30 L A Walsh [this message]
2021-10-26 0:48 ` xfsrestore'ing from file backups don't restore...why not? Dave Chinner
[not found] ` <617B5DA3.7060106@tlinx.org>
2021-10-29 19:24 ` L A Walsh
2021-10-31 21:28 ` L A Walsh
2021-11-01 20:23 ` cause of xfsdump msg: root ino 192 differs from mount dir ino 256 L A Walsh
2021-11-01 21:12 ` Dave Chinner
2021-11-02 1:35 ` L A Walsh
2021-11-02 1:47 ` L A Walsh
2021-11-02 4:45 ` L A Walsh
2021-11-02 14:24 ` xfsrestore'ing from file backups don't restore...why not? Eric Sandeen
2021-11-01 19:39 ` cause of xfsdump msg: root ino 192 differs from mount dir ino 256 L A Walsh
2021-11-02 14:29 ` Eric Sandeen
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=617721E0.5000009@tlinx.org \
--to=xfs@tlinx.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