Re: dump broken with new kernel
From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 12/08/04
- Previous message: Stefan Ehmann: "ext2fs oddness"
- In reply to: Andre Guibert de Bruet: "Re: dump broken with new kernel"
- Next in thread: Andre Guibert de Bruet: "Re: dump broken with new kernel"
- Reply: Andre Guibert de Bruet: "Re: dump broken with new kernel"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Andre Guibert de Bruet <andy@siliconlandmark.com> Date: Wed, 08 Dec 2004 12:55:23 +0100
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.
-- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Stefan Ehmann: "ext2fs oddness"
- In reply to: Andre Guibert de Bruet: "Re: dump broken with new kernel"
- Next in thread: Andre Guibert de Bruet: "Re: dump broken with new kernel"
- Reply: Andre Guibert de Bruet: "Re: dump broken with new kernel"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|