Re: Vinum problems in 5.3-BETA7?

2004-10-08 Thread Paul Mather
On Fri, 2004-10-08 at 07:52, Patrick M. Hausen wrote:

 We have a production system that runs on a vinum system drive
 configured like this:

[[Configuration omitted.]]

 It's currently running fine with FreeBSD 5.2.1-RELEASE-p10.
 
 After upgrading to 5.3-BETA7, buildworld, buildkernel, installkernel
 and reboot the system stops:
 
 vinum: loaded
 vinum: no drives found
 
 That's it. Of course it complains that it can't mount /dev/vinum/root.
 
 The list of detected GEOM devices at the mountroot  prompt
 includes ad0s1h, ad1s1h, ad0s1, ad1s1, ad0, ad1 and some more
 partitions.
 
 
 Where do I go from here? Is this expected behaviour due to the ongoing
 GEOM changes or should I go read Greg's how to debug vinum problems
 document? I will do that, no problem. Just want to know if it makes
 sense at all, because now everyone might tell me vinum is known broken in
 5.3 or similar.

Vinum is known broken in 5.3. :-)  You should be using geom_vinum
instead.  It will largely be a drop-in replacement for your above Vinum
configuration.  (I am using it on a similar root-on-vinum setup.)  The
main changes are these:

1) Load geom_vinum in /boot/loader.conf, e.g., add
'geom_vinum_load=YES' to /boot/loader.conf.  This will auto-detect
your Vinum on-disk configuration during boot.  You don't need any
rc.conf glue with geom_vinum.

2) Change vinum to gvinum in /etc/fstab.  E.g., use
/dev/gvinum/root instead of /dev/vinum/root

3) The userland utility is gvinum instead of vinum.

I am using geom_vinum on a root-on-vinum configuration under 6-CURRENT
since before RELENG_5 was branched, and I believe the same holds true
for RELENG_5 and HEAD as far as the above three points are concerned.

I don't know if there are plans to replace vinum entirely with gvinum
(and drop the g prefix) for 5.3-RELEASE.  Lukas Ertl would know.

Cheers,

Paul.
-- 
e-mail: [EMAIL PROTECTED]

Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid.
--- Frank Vincent Zappa

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Vinum problems in 5.3-BETA7?

2004-10-08 Thread Frank Mayhar
Paul Mather wrote:
 Vinum is known broken in 5.3. :-)  You should be using geom_vinum
 instead.  It will largely be a drop-in replacement for your above Vinum
 configuration.  (I am using it on a similar root-on-vinum setup.)  The
 main changes are these:

What I need to know is whether the raid5 support in gvinum is solid, yet.
I would dearly love to move my desktop system from 4-stable to RELENG_5,
but I have two rather large vinum raid5 filesystems that I really need to
keep.  Is anyone actually using raid5 with gvinum on RELENG_5?  If so,
how stable is it?  (The last I heard, there were still potential data
corruption problems, but I'm hoping that those have been fixed by now.)
-- 
Frank Mayhar [EMAIL PROTECTED]  http://www.exit.com/
Exit Consulting http://www.gpsclock.com/
http://www.exit.com/blog/frank/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]