So why is this crashing?
I just had it happen again -- something killed off the window it was
executing in -- system didn't go down, but it got a hangup -- a
cleaner shutdown -- but it still doesn't recover.
Under what circumstances should this work? Or does it work?
Linda A. Walsh wrote:
Due to another bug in lvm, my restore of this partition crashed after running a few
hours (takes alot longer to restore than to backup).
So I decided to use the "-R" option to Resume my previously left off dump:
# xfsrestore -R -p 180 -f /backups/Ishtar/torrents/torrents-100629-0-1611.dump .
xfsrestore: using file dump (drive_simple) strategy
xfsrestore: version 3.0.4 (dump format 3.0) - Running single-threaded
xfsrestore: resuming restore previously begun Wed Jun 30 04:41:57 2010
xfsrestore: examining media file 0
xfsrestore: seeking past portion of media file already restored
Looks good so far!..Yup, and..
xfsrestore: drive_simple.c:770: do_seek_mark: Assertion `nreadneeded64 <= ( ( intgen_t ) ( ( ( 1ull << ( ( unsigned long long )sizeof( intgen_t ) * ( unsigned long long )8 - ( 1ull + 1ull ))) - 1ull ) * 2ull + 1ull ))' failed.
Aborted (core dumped)
Say what? Um...is that supposed to be an error message?
Why can't it just tell me why "'nreadneeded64' > 0xbfffffffffffffd"
is 'bad', or what it means?
I have a feeling that the 'core dumped' message means that
if I want my filesystem restored in the near future, I should
just restart...
*sigh*
-l
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
