All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Kendall <wkendall@sgi.com>
To: Tommy Wu <wu.tommy@gmail.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: xfsrestore: WARNING: corrupt extent header
Date: Mon, 13 Feb 2012 13:14:22 -0600	[thread overview]
Message-ID: <4F39610E.5070601@sgi.com> (raw)
In-Reply-To: <CAGdb-8fFOAOSZAZNJDB9kyQJHoWKh+4SUohZfkknLDkaGnQFcQ@mail.gmail.com>

Could you please send me the output of xfsrestore using -v 4?
It'll probably be a lot of output, so compressing and attaching
it would be best.

Thanks,
Bill

On 02/12/2012 10:46 PM, Tommy Wu wrote:
> Hi!
>
>     OS: Debian squeeze amd64
>     xfsdump 3.0.6
>     xfsprogs 3.1.7
>
>     It happen when the xfsdump got message like:
> /sbin/xfsdump: WARNING: could not open regular file ino 33905028 mode
> 0x00008180: Stale NFS file handle: not dumped
> /sbin/xfsdump: WARNING: could not get list of non-root attributes for
> nondir ino 33905028: Stale NFS file handle (116)
> /sbin/xfsdump: WARNING: could not get list of root attributes for
> nondir ino 33905028: Stale NFS file handle (116)
> /sbin/xfsdump: WARNING: could not get list of secure attributes for
> nondir ino 33905028: Stale NFS file handle (116)
>
>     when I restore the dump file, it will get this, and it's not
> restore all files in the dump file:
> xfsrestore: WARNING: corrupt extent header
> xfsrestore: WARNING: unable to resync media file: some portion of dump
> will NOT be restored
>
>
>     for example:
> cmd: /sbin/xfsdump -l 0 -o -p 300 -J -F -M weekly_backup -L var -
> /dev/sda8 | /bin/gzip -qv | /usr/bin/split -b 1024m --verbose -
> /vol/backup/fw1/dump.20120211/var.xfsdump.gz.
> /sbin/xfsdump: using file dump (drive_simple) strategy
> /sbin/xfsdump: version 3.0.6 (dump format 3.0) - Running single-threaded
> /sbin/xfsdump: level 0 dump of fw1.teatime.com.tw:/var
> /sbin/xfsdump: dump date: Sat Feb 11 00:17:41 2012
> /sbin/xfsdump: session id: 54572680-8778-49e0-b6bd-635747c47de3
> /sbin/xfsdump: session label: "var"
> /sbin/xfsdump: ino map phase 1: constructing initial dump list
> /sbin/xfsdump: ino map phase 2: skipping (no pruning necessary)
> /sbin/xfsdump: ino map phase 3: skipping (only one dump stream)
> /sbin/xfsdump: ino map construction complete
> /sbin/xfsdump: estimated dump size: 598793856 bytes
> /sbin/xfsdump: creating dump session media file 0 (media 0, file 0)
> /sbin/xfsdump: dumping ino map
> /sbin/xfsdump: dumping directories
> /sbin/xfsdump: dumping non-directory files
> /sbin/xfsdump: WARNING: could not open regular file ino 33905028 mode
> 0x00008180: Stale NFS file handle: not dumped
> /sbin/xfsdump: WARNING: could not get list of non-root attributes for
> nondir ino 33905028: Stale NFS file handle (116)
> /sbin/xfsdump: WARNING: could not get list of root attributes for
> nondir ino 33905028: Stale NFS file handle (116)
> /sbin/xfsdump: WARNING: could not get list of secure attributes for
> nondir ino 33905028: Stale NFS file handle (116)
> /sbin/xfsdump: ending media file
> /sbin/xfsdump: media file size 549085392 bytes
> /sbin/xfsdump: dump size (non-dir files) : 543886560 bytes
> /sbin/xfsdump: dump complete: 46 seconds elapsed
> /sbin/xfsdump: Dump Status: SUCCESS
>   60.6%
> creating file `/vol/backup/fw1/dump.20120211/var.xfsdump.gz.aa'
>
> then test or restore from this dump file:
> mail:/vol/backup/fw1/dump.20120211# cat var.xfsdump.gz.aa | gzip -dqv
> | xfsrestore -v silent -p 300 -J -t - | grep ^xfsrestore:
> xfsrestore: WARNING: corrupt extent header
> xfsrestore: WARNING: unable to resync media file: some portion of dump
> will NOT be restored
>
>
>     It seems only happen in /var partition, and it's not always happen.
>

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

  reply	other threads:[~2012-02-13 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  4:46 xfsrestore: WARNING: corrupt extent header Tommy Wu
2012-02-13 19:14 ` Bill Kendall [this message]
2012-02-13 20:26   ` Bill Kendall
2012-02-13 23:10 ` [PATCH] xfsdump: handle files with no extent headers Bill Kendall

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=4F39610E.5070601@sgi.com \
    --to=wkendall@sgi.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.