Date: Fri, 9 Jul 2004 16:10:26 GMT From: Paul Frommeyer <paul@palas.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/67723: FreeBSD 5.x restore cannot handle other platforms/Linux(extfs)-dumps anymore Message-ID: <200407091610.i69GAQPW095896@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/67723; it has been noted by GNATS.
From: Paul Frommeyer <paul@palas.com>
To: <freebsd-gnats-submit@freebsd.org>, <ag-freebsd@space.net>
Cc:
Subject: Re: bin/67723: FreeBSD 5.x restore cannot handle other
platforms/Linux(extfs)-dumps anymore
Date: Fri, 09 Jul 2004 12:06:36 -0400
Hello,
I wanted to offer some supplemental information that I suspect is wider
behavior for this same bug. On 5.2.1-RC, recognition of legacy filesystems
appears to be broken, up to and including refusal of restore to recognize
the -c switch:
milo2.palas.com:/local/dump#uname -v
FreeBSD 5.2.1-RC #0: Sat Jan 31 05:36:22 GMT 2004
root@cypress.btc.adpatec.com:/usr/obj/usr/src/sys/GENERIC
milo2.palas.com:/local/dump#file sunosdump
sunosdump: dump format, 4.2 or 4.3 BSD without IDC
milo2.palas.com:/local/dump#restore -rf sunosdump
Tape is not a dump tape
milo2.palas.com:/local/dump#restore -c -r -f sunosdump
restore: illegal option -- c
usage: restore -i [-cdhmNuvy] [-b blocksize] [-f file] [-s fileno]
restore -r [-cdNuvy] [-b blocksize] [-f file] [-s fileno]
restore -R [-cdNuvy] [-b blocksize] [-f file] [-s fileno]
restore -x [-cdhmNuvy] [-b blocksize] [-f file] [-s fileno] [file ...]
restore -t [-cdhNuvy] [-b blocksize] [-f file] [-s fileno] [file ...]
milo2.palas.com:/local/dump#restore -c
restore: illegal option -- c
usage: restore -i [-cdhmNuvy] [-b blocksize] [-f file] [-s fileno]
restore -r [-cdNuvy] [-b blocksize] [-f file] [-s fileno]
restore -R [-cdNuvy] [-b blocksize] [-f file] [-s fileno]
restore -x [-cdhmNuvy] [-b blocksize] [-f file] [-s fileno] [file ...]
restore -t [-cdhNuvy] [-b blocksize] [-f file] [-s fileno] [file ...]
milo2.palas.com:/local/dump#
I found that an eminently effective workaround was to just use the 4.10
restore binary. I'm in the process of upgrading to 5.2.1-RELEASE, I'll post
another update if I notice different behavior with it.
I hope this information is helpful.
--Paul
Paul's Fone Company http://www.palas.com corwin@palas.com
Terabit routing, Peering, Metro Ethernet, Content Networking, CCIE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407091610.i69GAQPW095896>