dump broken with new kernel

Andre Guibert de Bruet andy at siliconlandmark.com
Thu Dec 9 21:45:20 PST 2004


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

> In message <20041207234332.Q637 at 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 at 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/    >


More information about the freebsd-current mailing list