Darryl Okahata wrote:
"Willem Jan Withagen" <[EMAIL PROTECTED]> write:Yep, the naming is the problem. Afaik due to the GEOM system newfs has changed. The vinum volume name must either end in '0' or 'a' to allow the newfs operation... however there is some message in current which says that someone (grog?) is working on it.
Vinum is running fine here on 5.0 for already quite some time.Nope. No joy:
the trick is most likely:
newfs -T ufs /dev/vinum/vinum0
# newfs -T ufs /dev/vinum/myvol
newfs: /dev/vinum/myvol: can't figure out file system partition
Since it's working for you, the problem is probably related to newfs
(existing vinum volumes are probably fine).
Arg. Out of desperation, I tried using "vinum0" as the volume
name, instead of "myvol". It worked (the "-T" isn't needed). Foo.
Arg.
--
didi
-------- http://checkrdf.sourceforge.net/ ---------
-> for your daily news needs on your FreeBSD box <-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message