From owner-freebsd-stable@FreeBSD.ORG Fri Apr 22 20:05:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E80BF16A4CE for ; Fri, 22 Apr 2005 20:05:28 +0000 (GMT) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0172043D49 for ; Fri, 22 Apr 2005 20:05:28 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j3MK5QKa015427 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 23 Apr 2005 06:05:26 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j3MK5P7l020816 for ; Sat, 23 Apr 2005 06:05:25 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j3MK5P0e020815 for freebsd-stable@freebsd.org; Sat, 23 Apr 2005 06:05:25 +1000 (EST) (envelope-from pjeremy) Date: Sat, 23 Apr 2005 06:05:25 +1000 From: Peter Jeremy To: freebsd-stable@freebsd.org Message-ID: <20050422200525.GG12673@cirb503493.alcatel.com.au> References: <20050422030748.GA64953@neptune.atopia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050422030748.GA64953@neptune.atopia.net> User-Agent: Mutt/1.4.2i Subject: Re: dump woes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 20:05:29 -0000 On Thu, 2005-Apr-21 23:07:48 -0400, Dan Ponte wrote: >I'm having a rather strange predicament with dump(8). First, I tried >dumping a snapshot to a file within the filesystem being dumped like so: > > styx# dump -0u -a -L -C 8 -f /usr/backup/usr.dump /usr > >I then let it sit for a while. The filesystem was only 4.1GB, but the >dump file was growing to almost 12GB! Try running fsck on the filesystem. It's possible that there's some corruption that's confusing dump. -- Peter Jeremy