public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Tommy Wu <wu.tommy@gmail.com>, xfs <xfs@oss.sgi.com>
Subject: Re: xfsrestore report SUCCESS but not restore all files in kernel 3.17
Date: Tue, 28 Oct 2014 23:09:19 -0500	[thread overview]
Message-ID: <5450686F.9070307@sandeen.net> (raw)
In-Reply-To: <CAGdb-8cnmCs=L0RPvE8+5jn3nmZoviiZtQBbo9S-BThA+3cBKg@mail.gmail.com>

On 10/28/14 11:06 PM, Tommy Wu wrote:
> 
> kernel 3.17.0 (same command in kernel 3.16.x work fine)
> xfsdump 3.1.4
> xfsprogs 3.2.1
> 
> test case:
> 1. create a new filesystem in LVM
> 
> lvcreate -L 5G -n test vg
> mkfs.xfs -f /dev/vg/test
> mount /dev/vg/test /mnt/x
> 
> 2. extract linux-3.17.tar.xz to the new filesystem
> 
> cd /mnt/x
> tar Jxvf /usr/src/linux-3.17.tar.xz
> 
> 3. backup the filesystem
> 
> xfsdump -l 0 -o -p 300 -J -F -M test -L test - /mnt/x | /bin/gzip -qv > /vol/test.xfsdump.gz
> 
> 4. test the dump file, it show a lots of NOTE, and it said restore status is SUCCESS.

Is this not the same bug we already discussed in your prior email,
"xfsdump not work in 3.17" ?  Are you testing with or without those bugfixes?

-Eric

> cat /vol/test.xfsdump.gz | gzip -dqv | xfsrestore -p 300 -J -t - | grep "^/sbin/xfsrestore:"
> /sbin/xfsrestore: using file dump (drive_simple) strategy
> /sbin/xfsrestore: version 3.1.4 (dump format 3.0)
> /sbin/xfsrestore: searching media for dump
> /sbin/xfsrestore: examining media file 0
> /sbin/xfsrestore: dump description:
> /sbin/xfsrestore: hostname: mail.teatime.com.tw <http://mail.teatime.com.tw>
> /sbin/xfsrestore: mount point: /mnt/x
> /sbin/xfsrestore: volume: /dev/mapper/vg-test
> /sbin/xfsrestore: session time: Wed Oct 29 11:45:54 2014
> /sbin/xfsrestore: level: 0
> /sbin/xfsrestore: session label: "test"
> /sbin/xfsrestore: media label: "test"
> /sbin/xfsrestore: file system id: d757277d-5167-4cdb-975d-c64b2f94a47e
> /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
> /sbin/xfsrestore: NOTE: ino 146 salvaging file, placing in orphanage/143.0/constraints.png.b64
> /sbin/xfsrestore: NOTE: ino 147 salvaging file, placing in orphanage/143.0/crop.gif.b64
> /sbin/xfsrestore: NOTE: ino 148 salvaging file, placing in orphanage/143.0/dvbstb.png.b64
> /sbin/xfsrestore: NOTE: ino 149 salvaging file, placing in orphanage/143.0/fieldseq_bt.gif.b64
> /sbin/xfsrestore: NOTE: ino 150 salvaging file, placing in orphanage/143.0/fieldseq_tb.gif.b64
> .... skip it....
> /sbin/xfsrestore: NOTE: ino 50363235 gen 1622742662 not referenced: placing in orphanage
> /sbin/xfsrestore: table of contents display complete: 3 seconds elapsed
> /sbin/xfsrestore: Restore Status: SUCCESS
> 
> 5. restore it, show a lots of NOTE, and resotre status is SUCCESS, but... compare them, it's different.
> 
> cat test.xfsdump.gz | gzip -dqv | xfsrestore -p 300 -J - /vol/x/
> /sbin/xfsrestore: using file dump (drive_simple) strategy
> /sbin/xfsrestore: version 3.1.4 (dump format 3.0)
> /sbin/xfsrestore: searching media for dump
> /sbin/xfsrestore: examining media file 0
> /sbin/xfsrestore: dump description:
> /sbin/xfsrestore: hostname: mail.teatime.com.tw <http://mail.teatime.com.tw>
> /sbin/xfsrestore: mount point: /mnt/x
> /sbin/xfsrestore: volume: /dev/mapper/vg-test
> /sbin/xfsrestore: session time: Wed Oct 29 11:45:54 2014
> /sbin/xfsrestore: level: 0
> /sbin/xfsrestore: session label: "test"
> /sbin/xfsrestore: media label: "test"
> /sbin/xfsrestore: file system id: d757277d-5167-4cdb-975d-c64b2f94a47e
> /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: restoring 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
> /sbin/xfsrestore: NOTE: ino 146 salvaging file, placing in orphanage/143.0/constraints.png.b64
> .... skip it....
> /sbin/xfsrestore: NOTE: ino 50363235 gen 1622742662 not referenced: placing in orphanage
> /sbin/xfsrestore: WARNING: unable to rmdir /vol/x//orphanage: Directory not empty
> /sbin/xfsrestore: restore complete: 3 seconds elapsed
> /sbin/xfsrestore: Restore Status: SUCCESS
> 
> 
> -- 
> 
> Tommy Wu
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-10-29  4:09 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 [this message]
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
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=5450686F.9070307@sandeen.net \
    --to=sandeen@sandeen.net \
    --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