From: L A Walsh <xfs@tlinx.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfsrestore'ing from file backups don't restore...why not?
Date: Sun, 31 Oct 2021 14:28:13 -0700 [thread overview]
Message-ID: <617F0A6D.6060506@tlinx.org> (raw)
In-Reply-To: <20211026004814.GA5111@dread.disaster.area>
When looking at a dump of /home (but not on other partitions
that I've noticed, I see (stopping listing on problem line)
XFSDUMP_OPTIONS=-J #(set externally , not usually)
>./dump1fs#160(Xfsdump)> xfsdump -b 268435456 -l 8 -L home -J - /home
xfsdump: using file dump (drive_simple) strategy
xfsdump: version 3.1.8 (dump format 3.0)
xfsdump: level 8 incremental dump of Ishtar:/home based on level 6 dump begun Fri Oct 29 04:30:13 2021
xfsdump: dump date: Sun Oct 31 14:20:37 2021
xfsdump: session id: 249233a0-a642-42a0-ae02-ed53012f3fa4
xfsdump: session label: "home"
xfsdump: NOTE: root ino 192 differs from mount dir ino 256, bind mount?
Of note, most things were placed in orphanage under
256.0
df shows:
df /home
Filesystem Size Used Avail Use% Mounted on
/dev/Space/Home2 2.0T 1.5T 570G 73% /home
(Became months ago as I made new partition of 2T to replace
old partition of 1.5T, after which I did another
level-0 backup.
next prev parent reply other threads:[~2021-10-31 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 21:30 xfsrestore'ing from file backups don't restore...why not? L A Walsh
2021-10-26 0:48 ` Dave Chinner
[not found] ` <617B5DA3.7060106@tlinx.org>
2021-10-29 19:24 ` L A Walsh
2021-10-31 21:28 ` L A Walsh [this message]
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=617F0A6D.6060506@tlinx.org \
--to=xfs@tlinx.org \
--cc=david@fromorbit.com \
--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