Date: Thu, 04 May 2000 01:08:16 +0900 From: Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp> To: Bob@WhiteBarn.Com Cc: Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp> Subject: Re: Dump, Vinum, and the Demise of /dev/rvinum Message-ID: <14608.20208.870.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> In-Reply-To: In your message of "Wed, 03 May 2000 07:28:04 -0500" <39101B54.AD14EF45@WhiteBarn.Com> References: <39101B54.AD14EF45@WhiteBarn.Com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 03 May 2000 07:28:04 -0500, Bob Van Valzah <Bob@WhiteBarn.Com> said: Bob> With 4.0-RELEASE, vinum apparently no longer offers both block and Bob> character device interfaces. This seems to confuse dump (though mount Bob> and fsck are unfazed and newfs needs the -v option). Bob> Snivey# dump 0f /dev/null /faithful Bob> DUMP: Cannot open /dev/vinum/rfaithful Bob> Snivey# dump 0f /dev/null /dev/vinum/faithful Bob> DUMP: Cannot open /dev/vinum/rfaithful dump(8) tends to generate the name of a raw device by inserting an 'r' after the last '/' of the device name. We should get rid of this conversion soon. Bob> So how do you dump a vinum filesystem? You can create a link to the node of a vinum volume, named 'r(volume name)'. eg cd /dev/vinum ; ln faithful rfaithful -- Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp> <tanimura@FreeBSD.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14608.20208.870.72159A>