Hi Bill, I have attached the xfsrestore version 3.0.1 last 20k log of my last dump file. I will be doing with version 3.0.5 of all three of my dumps (all three are bad, I got 32 GB, 44 GB and 49 GB back). Please let me know if this is useful. Thank you. GL --- On Tue, 30/8/11, Bill Kendall <wkendall@xxxxxxx> wrote: > From: Bill Kendall <wkendall@xxxxxxx> > Subject: Re: xfsrestore Does Only Only Partial Restore > To: "Gim Leong Chin" <chingimleong@xxxxxxxxxxxx> > Cc: xfs@xxxxxxxxxxx > Date: Tuesday, 30 August, 2011, 12:44 AM > 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@xxxxxxx> > wrote: > > > >> From: Bill Kendall <wkendall@xxxxxxx> > >> Subject: Re: xfsrestore Does Only Only Partial > Restore > >> To: "Gim Leong Chin" <chingimleong@xxxxxxxxxxxx> > >> Cc: xfs@xxxxxxxxxxx > >> 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@xxxxxxxxxxx > >> http://oss.sgi.com/mailman/listinfo/xfs > >> > > > > _______________________________________________ > xfs mailing list > xfs@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs >
Attachment:
xfsrestore3.0.1v5_rat18Aug2011_tail20k.gz
Description: GNU Zip compressed data
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
