ad0 vs. ad0s1 (was Re: vinum troubles on 5.3)

2004-11-12 Thread Brian Szymanski
> That's strange. What is the output of > > fdisk ad0 > bsdlabel ad0s1 > > Maybe something in GEOM gets confused... > > If the disappearing device node problem is fixed, gvinum should work in > this case. -bash-2.05b# bsdlabel ad0 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsi

Re: vinum troubles on 5.3

2004-11-11 Thread Stijn Hoop
Hi, On Thu, Nov 11, 2004 at 10:44:10PM -0500, Brian Szymanski wrote: > After a long and happy time with vinum under 4.8 -> 4.10, I'm finding > things very broken in 5.3. The config I'm trying to accomplish is > relatively simple, just a root mirrored volume configuration which worked > under 4.x.

vinum troubles on 5.3

2004-11-11 Thread Brian Szymanski
Howdy... After a long and happy time with vinum under 4.8 -> 4.10, I'm finding things very broken in 5.3. The config I'm trying to accomplish is relatively simple, just a root mirrored volume configuration which worked under 4.x. drive M1 device /dev/ad0s1e drive M2 device /dev/ad2s1e volume roo