restore(1) dumpfile to directory rather than filesystem -- possible? -- SOLVED

[Jerry McAllister]

On Tue, Jan 29, 2008 at 04:36:41PM +0100, Mel wrote:

> On Tuesday 29 January 2008 15:50:21 Alex Zbyslaw wrote:
> > Mel wrote:
> > >man restore:
> > >-r      Restore (rebuild a file system).
> > >
> > >This will recreate the filesystem, meaning, the files extracted will have
> > >identical inode numbers as on the original filesystem. Thus, you will very
> > >likely run into problems when using this mode.
> > >
> > >You're looking for -x, which extracts a dump file, similar to a tar,
> > > restoring ownership, file times and so on, but leaving the inode numbers
> > > up to the OS.
> > >
> > >restore -x is essentially what OP did interactively.
> >
> > Err, no.  Not unless it changed recently and this text is still
> > apparently present in 8-CURRENT (according to the Web interface).
> >
> >  From the man page BUGS section (though it's been there so long it's a
> > feature, in my book and belongs better with the -r option to prevent
> > exactly the confusion you've experienced).
> 
> Ever tried -r in a directory on a non-new filesystem? I don't recall the exact 
> error, but it can clash. Done restore -x for testing ever since.

Done so many times.   Never had a problem with it.

////jerry

> 
> >      A level zero dump must be done after a full restore.  Because restore
> >      runs in user code, it has no control over inode allocation; thus a
> > full dump must be done to get a new set of directories reflecting the new
> > inode numbering, even though the contents of the files is unchanged.
> 
> Ah, maybe it's the directories that contain the inode numbers of the old 
> filesystem. Whatever the cause - restore -r *should* only be used on a 
> newfs(8)'d filesystem.
> -- 
> Mel
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"