Date: Sat, 18 Apr 1998 03:22:41 +0400 From: "Mikhail A. Sokolov" <mishania@demos.su> To: Tom <tom@uniserve.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: dump/restore and large filesystem problems Message-ID: <19980418032241.40294@demos.su> In-Reply-To: <Pine.BSF.3.96.980417135448.18612G-100000@shell.uniserve.com>; from Tom <tom@uniserve.com> on Fri, Apr 17, 1998 at 01:55:25PM -0700 References: <Pine.BSF.3.96.980417135448.18612G-100000@shell.uniserve.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I reported bin/4683 PR on October, 3, 1997, it's still open and I didn't get any idea myself aswell. As it's written there, the workaround is -S [g,gnu]tar option. Which is "hadle sparse files efficiently" - dump can't. This was checked on 2.1.5, 2-2-some-beta, 3-0-some-snap . On Fri, Apr 17, 1998 at 01:55:25PM -0700, Tom wrote: # I'm attempting to backup a 32GB filesystem (about 8GB used) with dump on # a 2.2.6-STABLE system. The problem is that "restore" can not read the # data back: # # root@pegasus# restore -t # Dump date: Fri Apr 17 05:15:00 1998 # Dumped from: the epoch # Level 0 dump of /bak on pegasus.uniserve.com:/dev/ccd0c # Label: none # hole in map # abort? [yn] Segmentation fault # root@pegasus# # # There is about a 3 second delay between the "abort?" prompt and when it # segfaults. # # I guess dump/restore still have large filesystem problems... # # # Tom # # # # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-stable" in the body of the message -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980418032241.40294>