Date: Wed, 25 Aug 2004 15:21:10 -0500 From: "Mario A. Doria" <mariodoria@yahoo.com> To: freebsd-current@freebsd.org Subject: Re: freebsd-current Digest, Vol 73, Issue 14 Message-ID: <200408251521.11019.mariodoria@yahoo.com> In-Reply-To: <20040825195832.6A29D16A523@hub.freebsd.org> References: <20040825195832.6A29D16A523@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yes, I meant 5.3 :-) > > So what's state is (g)vinum likely to be in for 5.3? I'm hesitant to > upgrade because it appears that the system is moving from under > vinum's feet, and gvinum isn't there yet. What are people who are > currently using vinum on earlier 5.x's going to do until gvinum is > finished? Well, I have two machines running RELENG_5 from yesterday. One machine has four SCSI disks, two in a concatenated volume and two in a mirrored volume. I created everything in vinum, rebooted and reloaded in gvinum, no problems. This machine has been running make -j16 buildworlds on that volume for the last 36 hours. In another, I had two disks with a concatenated volume, and because I had two vinum drives in each disk, all hell broke loose. It wouldn't recognize the proper size of the volume, lose information, report disks as crashed and after a reboot, report everything was fine. I could reconfigure the vinum configuration using "vinum", and it would run OK until a reboot. Now I only have one vinum drive per disk, but still I have problems. I'm going to reformat the disks and start over. Mario
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408251521.11019.mariodoria>