From owner-freebsd-stable@FreeBSD.ORG Mon Sep 1 16:06:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F46D1065772 for ; Mon, 1 Sep 2008 16:06:45 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id EA28D8FC15 for ; Mon, 1 Sep 2008 16:06:44 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m81G6TAf039865; Mon, 1 Sep 2008 12:06:30 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m81G6Sfq047073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Sep 2008 12:06:28 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200809011606.m81G6Sfq047073@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 01 Sep 2008 12:06:35 -0400 To: "Kevin Oberman" From: Mike Tancsa In-Reply-To: <20080901160013.0005F4500F@ptavv.es.net> References: <20080901160013.0005F4500F@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Derek =?iso-8859-1?Q?Kuli=C5=84ski?= , Michael , freebsd-stable@freebsd.org Subject: Re: bin/121684: : dump(8) frequently hangs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2008 16:06:45 -0000 At 12:00 PM 9/1/2008, Kevin Oberman wrote: >I have a 7-Stable system which has not been able to successfully dump(8) >for about 2 months. Since it contains almost no important data that is >subject to change, it's not too big a deal, but I worry that other >systems might start showing the same problems. How does it actually fail ? Do the dump processes stall, or does it error out ? Did you fsck the file system ? I have seen dump fail when the file system is dirty. Also, I am not using snapshots. The flags I use are /sbin/dump -C24 -${BACKUP_LEVEL}anuf - /zoo | /usr/bin/gzip | dd of=/backup/zoo-level-${BACKUP_LEVEL}.gz ---Mike