Date: Sat, 23 Jan 1999 06:24:17 +0800 From: Peter Wemm <peter@netplex.com.au> To: Greg Lehey <grog@lemis.com> Cc: Jake <jake@checker.org>, current@FreeBSD.ORG Subject: Re: vinum read no longer works Message-ID: <199901222224.GAA36415@spinner.netplex.com.au> In-Reply-To: Your message of "Sat, 23 Jan 1999 08:17:08 %2B1030." <19990123081708.I5697@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey wrote: > On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: > > I can no longer bring up my vinum volume with the vinum read > > command: > > > > vinum read /dev/wd0s1e /dev/wd2s1f > > vinum read /dev/wd0s1e > > vinum read /dev/wd2s1f > > > > all come back with > > vinum: no drives > > Correct. As I explained in detail in my HEADS UP message a couple of > days ago, you must now specify drives, not partitions. The correct > command might be > > vinum read /dev/wd0 /dev/wd2 Does vinum scan the slices? What if there are two freebsd slices? From vinumhdr.h, it looks like it totally ignores slices. If somebody is working on a disk shared with something else (eg: DOS/windoze), then perhaps the examples should be: vinum read /dev/wd0s1 /dev/wd2s1 Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901222224.GAA36415>