Hi,
I just tried the 26 Aug 2011 commited version of xfsrestore from xfsdump, I got the same message:
xfsrestore: content.c:7510: restore_extent_group: Assertion `ehdr.eh_type == 4' failed.
Aborted
It is interesting that two different back-ups are corrupt after around 44 to 49 GB, more than half of the back-ups!
I did not look at /var/log/messages or dmesg while doing the back-ups. I only saw that the xfsdump session was successful.
GL
--- On Mon, 29/8/11, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> From: Dave Chinner <david@xxxxxxxxxxxxx>
> Subject: Re: xfsrestore Does Only Only Partial Restore
> To: "Gim Leong Chin" <chingimleong@xxxxxxxxxxxx>
> Cc: xfs@xxxxxxxxxxx
> Date: Monday, 29 August, 2011, 1:00 PM
> On Sun, Aug 28, 2011 at 08:31:40PM
> +0800, 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:
>
> ....
> > I downloaded xfsdump-3.0.5.tar.gz, did a build, and
> tried to do a restore using the newly built xfsrestore:
>
> > {>
> > optimus:/home/chingl/archive/rat #
> /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore -f
> ./rat18Aug2011 /tmp/mnt3
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> using file dump (drive_simple) strategy
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> version 3.0.5 (dump format 3.0) - Running single-threaded
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> searching media for dump
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> examining media file 0
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> dump description:
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> hostname: rat
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> mount point: /home
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> volume: /dev/sdb3
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> session time: Thu Aug 18 12:57:36 2011
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> level: 0
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> session label: "rat_18Aug2011"
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> media label: "rat18Aug2011"
> >
> 3>/home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore: file
> system id: f3b08587-cf98-4b7b-99b0-dc9d4e77b631
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> session id: d8069cd0-a092-4fb2-b378-0eda33474aae
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> media id: 96370000-6e2c-40eb-9c3c-93ca42de7524
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> searching media for directory dump
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> reading directories
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> 90820 directories and 539579 entries processed
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> directory post-processing
> > /home/chingl/XFS/xfsdump-3.0.5/restore/xfsrestore:
> restoring non-directory files
> > xfsrestore: content.c:7510:
> restore_extent_group: Assertion `ehdr.eh_type == 4' failed.
>
> Which indicates that the dump file on your external drive
> is
> probably corrupt. xfs_restore only has a certain number of
> known
> extent types, and this ASSERT failure occurs if the extent
> type is
> not valid - the restore code has checked for all special
> types,
> and is now expecting a data extent, which it isn't. That's
> where the
> restore will stop.
>
> All the other restore attempts you've made have equivalent
> "failed
> to read" errors that also indicate some kind of corruption
> in the
> dump file.
>
> > (>Aborted 2>optimus:/home/chingl/archive/rat #
> >
> >
> > Could some one please assist to enlighten me what is
> going on, why
> > does the restoration fail? The xfsdump session
> looked OK.
>
> Well, I can't tell you if the dump was ok or not without
> that
> output. Even if the dump was successful, it could have
> easily been
> corrupted by a memory or other hardware bit error on the
> way to
> disk. Were there any IO errors reported in the kernel dmesg
> messages
> while the dump was being taken?
>
> > Is there any way I can extract back my /home back
> up? This is my
> > only back up copy. i have two other xfsdump dump
> files taken
> > earlier, I have not tried those.
>
> No idea, you'll have to wait for the xfsdump experts to
> come online.
>
> > Is xfsdump and xfsrestore really robust for dump to
> regular file,
> > or should I have done a tar instead?
>
> It should be fine, but if there was a hardware related
> problem then
> all bets are off...
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@xxxxxxxxxxxxx
>
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
