From owner-freebsd-current@FreeBSD.ORG  Fri Dec 10 05:45:20 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 608AC16A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 10 Dec 2004 05:45:20 +0000 (GMT)
Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com
	[209.69.98.4])	by mx1.FreeBSD.org (Postfix) with ESMTP id EA36C43D48
	for <freebsd-current@freebsd.org>;
	Fri, 10 Dec 2004 05:45:19 +0000 (GMT)
	(envelope-from andy@siliconlandmark.com)
Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1])
	iBA5jGQ5019803;	Fri, 10 Dec 2004 00:45:16 -0500 (EST)
	(envelope-from andy@siliconlandmark.com)
Received: from localhost (andy@localhost)iBA5jDdP019800;
	Fri, 10 Dec 2004 00:45:16 -0500 (EST)
	(envelope-from andy@siliconlandmark.com)
X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing
	-bs
Date: Fri, 10 Dec 2004 00:45:13 -0500 (EST)
From: Andre Guibert de Bruet <andy@siliconlandmark.com>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
In-Reply-To: <23033.1102506923@critter.freebsd.dk>
Message-ID: <20041210004250.I637@alpha.siliconlandmark.com>
References: <23033.1102506923@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
cc: freebsd-current@freebsd.org
Subject: Re: dump broken with new kernel
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2004 05:45:20 -0000


On Wed, 8 Dec 2004, Poul-Henning Kamp wrote:

> In message <20041207234332.Q637@alpha.siliconlandmark.com>, Andre Guibert de Br
> uet writes:
>
>> I am still running into dump problems on my system. I'm using:
>> $FreeBSD: src/sys/kern/vfs_mount.c,v 1.168 2004/12/07 08:15:40 phk Exp $
>> $FreeBSD: src/sys/sys/mount.h,v 1.187 2004/12/07 08:15:40 phk Exp $
>>
>> FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Dec  7 23:02:43
>> EST 2004     root@bling.home:/usr/CURRENT/sys/i386/compile/BLING  i386
>>
>> # /sbin/dump -0uaLf "/mnt/backups/`hostname -s`-`utime`-amrd0a.dump" /mnt/amrd0a
>> mksnap_ffs: Cannot create /mnt/amrd0a/.snap/dump_snapshot: Bad address
>> dump: Cannot create /mnt/amrd0a/.snap/dump_snapshot: No such file or directory
>
> Ok, should work now.

It appears to have fixed it. I'm now debugging the amr(4) driver as it 
hangs with a "bad slot 0 completed" message. From the source, that number 
could be any positive integer, but i've never seen it hang with anything 
other than 0 (I've reproduced the problem about 10 times already). It's 
fun stuff... :-)

Thanks,
Andy

| Andre Guibert de Bruet | Enterprise Software Consultant >
| Silicon Landmark, LLC. | http://siliconlandmark.com/    >