From owner-freebsd-questions Wed May 3 5:28:12 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.whitebarn.com (Spin.WhiteBarn.com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 90F9537B963 for ; Wed, 3 May 2000 05:28:07 -0700 (PDT) (envelope-from Bob@WhiteBarn.Com) Received: from WhiteBarn.Com (Relent.Bob.WhiteBarn.Com [216.0.13.50]) by smtp.whitebarn.com (8.9.3/8.9.3) with ESMTP id HAA15167; Wed, 3 May 2000 07:28:05 -0500 (CDT) (envelope-from Bob@WhiteBarn.Com) Message-ID: <39101B54.AD14EF45@WhiteBarn.Com> Date: Wed, 03 May 2000 07:28:04 -0500 From: Bob Van Valzah X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freeBSD-Questions Subject: Dump, Vinum, and the Demise of /dev/rvinum Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With 4.0-RELEASE, vinum apparently no longer offers both block and character device interfaces. This seems to confuse dump (though mount and fsck are unfazed and newfs needs the -v option). Consider this excerpt from /etc/fstab: # Device Mountpoint FStype Options Dump Pass# /dev/vinum/faithful /faithful ufs rw 2 6 Now see what happens when I try to run dump: Snivey# dump 0f /dev/null /faithful DUMP: Date of this level 0 dump: Wed May 3 07:24:39 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/vinum/rfaithful (/faithful) to /dev/null DUMP: Cannot open /dev/vinum/rfaithful Same story if I name the device instead of the mount point: Snivey# dump 0f /dev/null /dev/vinum/faithful DUMP: Date of this level 0 dump: Wed May 3 07:24:55 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/vinum/rfaithful (/faithful) to /dev/null DUMP: Cannot open /dev/vinum/rfaithful So how do you dump a vinum filesystem? Thanks, Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message