From owner-freebsd-stable@FreeBSD.ORG Tue Jan 4 20:51:57 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 7471016A4CE for ; Tue, 4 Jan 2005 20:51:57 +0000 (GMT) Received: from shrewd.pub.knigma.org (shrewd.pub.knigma.org [81.2.102.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8054643D1D for ; Tue, 4 Jan 2005 20:51:56 +0000 (GMT) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lap.wireless.knigma.org [217.169.23.236]) by shrewd.pub.knigma.org (8.13.1/8.13.1) with ESMTP id j04KptDS008527 for ; Tue, 4 Jan 2005 20:51:55 GMT (envelope-from markk@knigma.org) Message-ID: Date: Tue, 4 Jan 2005 20:51:41 +0000 To: freebsd-stable@freebsd.org From: Mark Knight References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain;charset=us-ascii;format=flowed User-Agent: Turnpike/6.04-U () Subject: Re: dump dumping core 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: Tue, 04 Jan 2005 20:51:57 -0000 In message , Mark Knight writes >With RELENG_5 from yesterday, as well from a week or so ago I'm finding >that dump is failing. Must admit, this is the first time I've tried to >run a backup since migrating from RELENG_4 to RELENG_5. > >fsck -f / marks the file system as clean. > >Any ideas? > >root@shrewd# dump -0a -b 512 -f - / > /dev/null The -b 512 (or other large values), seems to be the key to making it crash (on various inodes). Sometimes the error is "master/slave protocol botched" instead. Until I find the cause, the workaround of "don't do that then" seems appropriate. At least it wasn't fs corruption ;) -- Mark A. R. Knight finger: markk@knigma.org Tel: +44 7973 410732 http://www.knigma.org/