From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 16:01:03 2004 Return-Path: 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 BC42E16A4CE for ; Mon, 6 Dec 2004 16:01:03 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E24443D1F for ; Mon, 6 Dec 2004 16:01:03 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id iB6G10dB000694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 6 Dec 2004 08:01:01 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 06 Dec 2004 08:01:01 -0800 To: current@freebsd.org From: Manfred Antar Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 16:01:03 -0000 When I try to do a dump of the root filesystem I get : mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument dump: Cannot create //.snap/dump_snapshot: No such file or directory A kernel from a week ago works fine. The command I'm using is: dump 0Lfua /dev/nsa0 /dev/ad0s1a The .snap directory does exist and it is: drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap ================================== || null@pozo.com || || Ph. (415) 681-6235 || ==================================