Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jun 2004 22:22:32 +0200 (CEST)
From:      Armin Gruner <ag-freebsd@space.net>
To:        FreeBSD-gnats-submit@FreeBSD.org
Cc:        ag-freebsd@space.net
Subject:   bin/67723: FreeBSD 5.x restore cannot handle other platforms/Linux(extfs)-dumps anymore
Message-ID:  <200406082022.i58KMWM7059179@hamming.space.net>
Resent-Message-ID: <200406082030.i58KUNwH058151@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         67723
>Category:       bin
>Synopsis:       FreeBSD 5.x restore cannot handle other platforms/Linux(extfs)-dumps anymore
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 08 20:30:23 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Armin Gruner
>Release:        FreeBSD 5.2.1-RELEASE-p6 i386
>Organization:
SpaceNet AG
>Environment:
System: FreeBSD hamming 5.2.1-RELEASE-p6 FreeBSD 5.2.1-RELEASE-p6 #1: Fri May 7 22:13:46 CEST 2004 ag@hamming:/usr/obj/usr/src/sys/SPACE i386

>Description:
	At some point between FreeBSD 4 and FreeBSD 5 versions of the "restore" utility,
	"restore" ceased to support reading dumps of other platforms, namely Linux-ext2fs-dumps.
	This makes using a FreeBSD 5.x system as a backup server system very unfriendly
	in a mixed environment.
	This was probably introduced when incorporating changes for UFS2 support.

>How-To-Repeat:
	Get a Linux-extfs filesystem dump, and try to restore it on a FreeBSD system:

	On a FreeBSD 4.9-RELEASE, restore works fine:

	[ag@moebius2 1054]$ uname -a
	FreeBSD moebius2 4.9-RELEASE-p4 FreeBSD 4.9-RELEASE-p4 #1: Wed Mar 24 23:44:34 CET 2004 
	   ag@dhcp-147.office:/usr/obj/usr/src/sys/SPACE_SMP  i386

	[ag@moebius2 1053]$ file linux.dump
	linux.dump: new-fs dump file (little endian), This dump Wed Jun  2 01:02:08 2004,
	Previous dump Sun May 30 00:52:59 2004, Volume 1, Level 1, type: tape header,
	Label /var, Filesystem /var, Device /dev/sda3, Host Swain, Flags 1

	[ag@moebius2 1055]$ restore ivbf 2 linux.dump
	Verify tape and initialize maps
	Dump   date: Wed Jun  2 01:02:08 2004
	Dumped from: Sun May 30 00:52:59 2004
	Level 1 dump of /var on Swain:/dev/sda3
	Label: /var
	Extract directories from tape
	Initialize symbol table.
	restore > ls
	.:
	     2 ./     125953 cache/ 220417 lock/  299137 run/
	     2 ../     31489 lib/    94465 log/   314881 spool/

	restore > quit


	Whereas on a FreeBSD-5.2.1-RELEASE, it fails:

	[ag@hamming 1073]$ uname -a
	FreeBSD hamming 5.2.1-RELEASE-p6 FreeBSD 5.2.1-RELEASE-p6 #1: Fri May  7 22:13:46 CEST 2004
	    ag@hamming:/usr/obj/usr/src/sys/SPACE  i386

	[ag@hamming 1074]$ file linux.dump
	linux.dump: new-fs dump file (little endian), This dump Wed Jun  2 01:02:08 2004,
	Previous dump Sun May 30 00:52:59 2004, Volume 1, Level 1, type: tape header,
	Label /var, Filesystem /var, Device /dev/sda3, Host Swain, Flags 1

	[ag@hamming 1075]$ restore ivbf 2 linux.dump
	Verify tape and initialize maps
	Dump   date: Thu Jan  1 01:00:10 1970
	Dumped from: the epoch
	Level 1 dump of /var on Swain:/dev/sda3
	Label: /var
	Extract directories from tape
	. is not on the tape
	Root directory is not on tape
	abort? [yn] y
	dump core? [yn] n
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406082022.i58KMWM7059179>