bin/66036: restore crashes (reproducable, core file and backtrace log available)

[mckusick at FreeBSD.org]

Synopsis: restore crashes (reproducable, core file and backtrace log available)

State-Changed-From-To: open->closed
State-Changed-By: mckusick
State-Changed-When: Fri May 23 19:35:04 UTC 2008
State-Changed-Why: 
To: Derek Kulinski <takeda at chinatsu.takeda.tk>
Subject: Re: FreeBSD bug report bin/66036: restore crashes 
--------
> Date: Fri, 23 May 2008 12:15:26 -0700
> From: Derek Kulinski <takeda at chinatsu.takeda.tk>
> To: Kirk McKusick <mckusick at mckusick.com>
> Subject: Re: FreeBSD bug report bin/66036: restore crashes
> 
> Hi Kirk,
> 
> On Fri, May 23, 2008 at 11:47:55AM -0700, Kirk McKusick wrote:
> > I am going through old FreeBSD bug reports trying to determine if
> > they are still relevant. You filed "bin/66036: restore crashes" on
> > Tue Apr 27 14:50:10 PDT 2004. There have been several patches to
> > restore that may have fixed this problem. I am writing to find out
> > if you have reason to believe that your reported bug is still present.
> > If not, I will close the bug report.
> 
> As far as I remember, the dump was generated on a live system
> (FBSD 4.x doesn't have snapshots), so the dump file was a bit broken.
> 
> Once I upgraded to 5.x+ I started using snapshots for the backup,
> I don't think I experienced any situation like that since then.
> 
> Though, I still think that restore shouldn't crash no matter what the
> dump file contained...
> 
> I guess there's no point in keeping the bug, though it seems
> that dump/restore aren't really as robust as other FBSD tools,
> which is a bit worrying since they're a bit important.
> 
> Each time I do backup I run restore wirth -n option to check it, but
> it still doesn't guarantee me that the backup will be 100% realiable.
> 
> Derek

Thanks for your report. I concur with you that restore should be as
robust as possible which is what has lead me on my current crusade
to track down all reported problems and try to ensure that they are
resolved. The net effect is that restore is now more robust than it
has been in the past, though I am sure that you can still find ways
to choke it up. When all else fails, it can be run with -D (debugging)
mode where it will do its best to keep going no matter what you feed it.

	Kirk McKusick


http://www.freebsd.org/cgi/query-pr.cgi?pr=66036