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: Fri, 31 Oct 2014 10:04:57 +1100 [thread overview]
Message-ID: <20141030230457.GK13323@dastard> (raw)
In-Reply-To: <CAGdb-8dt23oO7nncZdtri1BeNyWkR-6UF_4QRZx2X-5+tFYSRw@mail.gmail.com>
On Thu, Oct 30, 2014 at 04:39:01PM +0800, Tommy Wu wrote:
> I'm confusing now...
>
> in the test VM and one of my machine, rebuild xfsdump/xfsprogs will make
> the test work.
I know why, too.
> the xfsdump command I use:
> xfsdump -v debug -l 0 -o -p 300 -J -F -M test -L test -f test.xfsdump
> /mnt/backup > xfsdump.log
> the log:
> https://mega.co.nz/#!xIhTjD6Y!Gwp_ilW5UyRiqn2DSxPTHM0TH5qBghMlKXAmHoWk2iQ
This indicates the bulkstat on the dump side was terminated
prematurely.
> the xfsrestore command I use:
> xfsrestore -v debug,tree=nitty -p 300 -J -f test.xfsdump /vol/backup/x/ >
> xfsrestore.log
> the log:
> https://mega.co.nz/#!oZIFWQST!VUY90EZ8XvZDYy9GwF5mqtQVtWNW90Sar5MZhNzGbYI
And the errors in the restore side are because there are missing
directory inodes in the dump, hence orphaning occurs.
It might take me a little while to come up with a fix - I've noticed
a few things that I need to check out in more detail in tracking
this down....
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-30 23:18 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
[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 [this message]
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=20141030230457.GK13323@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.