Date: Wed, 15 Nov 1995 21:55:33 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: sysseh@devetir.qld.gov.au (Stephen Hocking) Cc: bugs@freebsd.org Subject: Re: Cannot interactively restore from a multivolume dump Message-ID: <199511152055.VAA08838@uriah.heep.sax.de> In-Reply-To: <199511150944.JAA17130@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at Nov 15, 95 07:44:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Stephen Hocking wrote: > I then tell it to extract, starting with the last volume when it > prompts me for the volume number. As each volume is processing, it > mumbles something about rsyncing & skipping a few blocks, and only > takes a tiny fraction of the time that it took to write each tape > i.e. it doesn't seem to be writing the full tape. ANybody else > noticed this? I've succesfully been using it. It's okay that it doesn't read the entire tape in order to find that it hasn't to deal with just that particular volume (that's one of the big advantages of dump/restore actually!). It simply tracks all i-node numbers that it wants to restore, and all it has to do for any volume is to examine the first header on it, and see if there's any actual work on this volume. (It does always write based on i-node number ordering.) So the question is: why did it think that your files haven't been on *any* volume? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511152055.VAA08838>