Date: Wed, 08 Dec 2004 12:55:23 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Andre Guibert de Bruet <andy@siliconlandmark.com> Cc: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel Message-ID: <23033.1102506923@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 07 Dec 2004 23:50:58 EST." <20041207234332.Q637@alpha.siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23033.1102506923>