From: Bill Kendall <wkendall@sgi.com>
To: Gim Leong Chin <chingimleong@yahoo.com.sg>
Cc: xfs@oss.sgi.com
Subject: Re: xfsrestore Does Only Only Partial Restore
Date: Mon, 29 Aug 2011 11:44:14 -0500 [thread overview]
Message-ID: <4E5BC1DE.6080506@sgi.com> (raw)
In-Reply-To: <1314635781.16065.YahooMailClassic@web77703.mail.sg1.yahoo.com>
Gim Leong Chin wrote:
> Hi Bill,
>
> Right now the log file is already over 500 MB and growing. Even after compression I do not think I can mail it as an attachment.
>
> Is there any other way that I can send you the log files?
If you could just send the last few thousand lines that should be sufficient.
If I do end up needing more than that I can provide an ftp drop for you.
Thanks,
Bill
>
>
> GL
>
> --- On Mon, 29/8/11, Bill Kendall <wkendall@sgi.com> wrote:
>
>> From: Bill Kendall <wkendall@sgi.com>
>> Subject: Re: xfsrestore Does Only Only Partial Restore
>> To: "Gim Leong Chin" <chingimleong@yahoo.com.sg>
>> Cc: xfs@oss.sgi.com
>> Date: Monday, 29 August, 2011, 10:11 PM
>> Gim Leong Chin wrote:
>>> Hi,
>>>
>>> This is the very first time I tried doing a xfsrestore
>> of a back up and I hit some serious trouble.
>>> I had openSUSE 11.1 (kernel 2.6.27) on my Acer
>> notebook. I did a xfsdump of /home to a WD My Passport
>> external USB hard drive with XFS on it.
>>> I installed openSUSE 11.4 (kernel 2.6.37), then tried
>> to do xfsrestore from the WD USB drive. The dump file
>> is 121 GB.
>>> I tried two times on two different days, but each time
>> the xfsrestore would stop writing at the exact same point,
>> 49 GB and say success at the end.
>>> I then copied the dump file to one hard drive on my
>> desk top, and did a dump to another hard drive, to
>> /tmp/mnt3. I get back identical messages:
>> ...
>>
>>> 9>xfsrestore: attempt to read 1008286921 bytes
>> failed: end of recorded data
>>
>> xfsdump breaks a file's data into "extents" that are a max
>> size of 16 MB.
>> The fact that this is trying to read almost 1 GB here
>> indicates that
>> the extend header is corrupt.
>>
>> ...
>>
>>> xfsrestore: content.c:7510:
>> restore_extent_group: Assertion `ehdr.eh_type == 4' failed.
>>
>> As Dave said, this also indicates a corrupt extent header.
>>
>> I'd recommend adding "-v 5" to your xfsrestore command line
>> and redirecting the
>> (very verbose) output to a file, and send that compressed
>> output to me or the
>> list. It'd be best to do this with more than one of your
>> dumps so we can see
>> if there's a pattern to where the corruption occurs.
>>
>> Bill
>>
>> _______________________________________________
>> 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
next prev parent reply other threads:[~2011-08-29 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 16:36 xfsrestore Does Only Only Partial Restore Gim Leong Chin
2011-08-29 16:44 ` Bill Kendall [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-30 3:06 Gim Leong Chin
2011-08-30 4:07 ` Bill Kendall
2011-08-28 12:31 Gim Leong Chin
2011-08-28 15:15 ` Gim Leong Chin
2011-08-29 3:53 ` Gim Leong Chin
2011-08-29 5:00 ` Dave Chinner
2011-08-29 5:47 ` Gim Leong Chin
2011-08-29 14:11 ` 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=4E5BC1DE.6080506@sgi.com \
--to=wkendall@sgi.com \
--cc=chingimleong@yahoo.com.sg \
--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