From owner-freebsd-stable Fri Apr 17 16:26:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06162 for freebsd-stable-outgoing; Fri, 17 Apr 1998 16:26:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA06101 for ; Fri, 17 Apr 1998 23:26:36 GMT (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yQKWa-00052V-00; Fri, 17 Apr 1998 16:26:28 -0700 Date: Fri, 17 Apr 1998 16:26:25 -0700 (PDT) From: Tom To: "Mikhail A. Sokolov" cc: freebsd-stable@FreeBSD.ORG Subject: Re: dump/restore and large filesystem problems In-Reply-To: <19980418032241.40294@demos.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sat, 18 Apr 1998, Mikhail A. Sokolov wrote: > 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 . But I don't have any sparse files on the filesystem (in fact, the filesystem just contains tar archive files). Also, tar backs up the filesystem properly, without special flags. Just a "tar c /filesystem" does it all. > 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: Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message