From: Dave Chinner <david@fromorbit.com>
To: Tommy Wu <wu.tommy@gmail.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: xfsrestore report SUCCESS but not restore all files in kernel 3.17
Date: Thu, 30 Oct 2014 08:25:56 +1100 [thread overview]
Message-ID: <20141029212556.GH13323@dastard> (raw)
In-Reply-To: <CAGdb-8cnmCs=L0RPvE8+5jn3nmZoviiZtQBbo9S-BThA+3cBKg@mail.gmail.com>
On Wed, Oct 29, 2014 at 12:06:10PM +0800, Tommy Wu wrote:
> /sbin/xfsrestore: session id: 6f114712-6fb6-4f35-a2f3-30ca1a0af5bb
> /sbin/xfsrestore: media id: 2eb2ff54-1838-47b2-a8d5-5f520deaf5f5
> /sbin/xfsrestore: searching media for directory dump
> /sbin/xfsrestore: reading directories
> /sbin/xfsrestore: 2035 directories and 33045 entries processed
> /sbin/xfsrestore: directory post-processing
> /sbin/xfsrestore: reading non-directory files
> /sbin/xfsrestore: NOTE: ino 144 salvaging file, placing in
> orphanage/143.0/Makefile
> /sbin/xfsrestore: NOTE: ino 145 salvaging file, placing in
> orphanage/143.0/bayer.png.b64
.....
> .... skip it....
> /sbin/xfsrestore: NOTE: ino 50363235 gen 1622742662 not referenced: placing
> in orphanage
FWIW, this can be expected behaviour if you run xfsdump on a live
filesystem. From the DIAGNOSTICS section of the xfsdump man page:
The message ``xfsdump: WARNING: unable to open directory:
ino N: Invalid argument'' can occur with filesystems which
are actively being modified while xfsdump is running.
This can happen to either directory or regular file inodes -
affected files will not end up in the dump, files below
affected directories will be placed in the orphanage
directory by xfsrestore.
This is exactly what you are seeing - files being placed in the
orphanage on restore because they appear to have no parent directory
inode referencing them.
IOWs, you're likely seeing the effect of the filesystem changing
while you are running xfsdump, not a bug in xfsdump or xfs_restore.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-29 21:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 4:06 xfsrestore report SUCCESS but not restore all files in kernel 3.17 Tommy Wu
2014-10-29 4:09 ` Eric Sandeen
2014-10-29 4:27 ` Tommy Wu
2014-10-29 4:28 ` Eric Sandeen
2014-10-29 4:30 ` Tommy Wu
2014-10-29 4:40 ` Dave Chinner
2014-10-29 6:46 ` Tommy Wu
2014-10-29 7:51 ` Dave Chinner
2014-10-29 9:03 ` Tommy Wu
2014-10-29 9:21 ` Tommy Wu
2014-10-29 10:33 ` Dave Chinner
2014-10-29 10:43 ` Dave Chinner
2014-10-29 12:32 ` Tommy Wu
2014-10-29 19:50 ` Dave Chinner
2014-10-29 20:52 ` Dave Chinner
2014-10-29 21:25 ` Dave Chinner [this message]
[not found] ` <CAGdb-8dbGRu_GWB4qoeNP8Kso2hzkLcuFS9Pwtnm2xOkP2T0rQ@mail.gmail.com>
2014-10-30 5:03 ` Dave Chinner
2014-10-30 8:39 ` Tommy Wu
2014-10-30 10:39 ` Tommy Wu
2014-10-30 23:04 ` Dave Chinner
2014-10-31 0:09 ` Dave Chinner
2014-10-31 1:51 ` Tommy Wu
2014-10-31 3:49 ` Dave Chinner
2014-10-31 4:25 ` Dave Chinner
2014-10-31 4:42 ` Tommy Wu
2014-10-31 4:55 ` Eric Sandeen
2014-10-31 5:40 ` Tommy Wu
2014-11-07 1:05 ` Tommy Wu
2014-11-07 4:37 ` Dave Chinner
2014-10-31 4:40 ` Tommy Wu
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=20141029212556.GH13323@dastard \
--to=david@fromorbit.com \
--cc=wu.tommy@gmail.com \
--cc=xfs@oss.sgi.com \
/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