From owner-freebsd-stable@FreeBSD.ORG Fri Apr 22 03:07:49 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 8D26416A4CE for ; Fri, 22 Apr 2005 03:07:49 +0000 (GMT) Received: from neptune.atopia.net (neptune.atopia.net [209.128.231.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54C3743D45 for ; Fri, 22 Apr 2005 03:07:49 +0000 (GMT) (envelope-from dcp1990@neptune.atopia.net) Received: by neptune.atopia.net (Postfix, from userid 1034) id 8B7F841C8; Thu, 21 Apr 2005 23:07:48 -0400 (EDT) Date: Thu, 21 Apr 2005 23:07:48 -0400 From: Dan Ponte To: freebsd-stable@freebsd.org Message-ID: <20050422030748.GA64953@neptune.atopia.net> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline User-Agent: Mutt/1.5.8i Subject: 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 03:07:49 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all. 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! I suspected recursion within the dump (even though it shouldn't happen, as I was dumping the snapshot, and the dump(8) code seems to create the snapshot and unlink it before any dumping starts). So, I mounted an NFS filesystem on my workstation and attempted to dump to it, like so: styx# dump -0u -a -L -C 8 -S -f /mnt/wksback/usr.dump /usr This time, it seemed to pause disk activity for a while, presumably while it copied out to the network (in the pervious instance, the disk activity LED was on constantly). My hopes were high until, again, the dump grew in size: 5.6G Apr 21 22:48 usr.dump I stopped the dump and ran the following for the hell of it: > tail usr.dump | strings styx.cox.net none /usr /dev/ad0s1f styx.cox.net none /usr /dev/ad0s1f (repeat...) Apparently, it's filling up the file with just NULLs and that! I am at a loss as to what is happening. Any insight in to the matter would be greatly appreciated. Thanks, -Dan --=20 Dan Ponte http://www.theamigan.net/ Brain, n.: The apparatus with which we think that we think. -- Ambrose Bierce, "The Devil's Dictionary" --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCaGqE8dUD8SpKFR8RAni0AKDaYuQEYQZ/mtbD8tuNS+XejZT4KQCfYtxy +ygPF6Ug8JNrdWQOJGcS05w= =gY4C -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ--