Date: Wed, 25 Mar 2009 17:11:39 +0100 From: Dimitry Andric <dimitry@andric.com> To: "Mikhail T." <mi+thun@aldan.algebra.com> Cc: freebsd-stable@freebsd.org, fs@freebsd.org Subject: Re: dump | restore fails: unknown tape header type 1853384566 Message-ID: <49CA57BB.2070409@andric.com> In-Reply-To: <49C87E0D.5090501@aldan.algebra.com> References: <49C83673.3000604@aldan.algebra.com> <200903241537.36515.doconnor@gsoft.com.au> <49C87E0D.5090501@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-03-24 07:30, Mikhail T. wrote: > dump a0f - /old | restore -rf - > [...] > DUMP: 17.25% done, finished in 3:27 at Tue Mar 24 05:42:00 2009 > DUMP: 20.36% done, finished in 3:09 at Tue Mar 24 05:28:13 2009 > DUMP: 23.83% done, finished in 2:50 at Tue Mar 24 05:14:32 2009 > unknown tape header type -621260722 > abort? [yn] > > Looks like a junk value somewhere... Unitialized variable or some such. Hmm, I can't reproduce this at all; I use dump and restore quite regularly in this way, and I have never encountered this issue (except for the occasional 'expected file NNN, got file MMM', which is usually harmless). Maybe the dump output gets corrupted in some way? (E.g. faulty RAM, or disk?) If you are dumping a live filesystem, could it possibly help to add the -L option?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49CA57BB.2070409>