Date: Wed, 11 Jan 2006 13:56:25 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Brian Szymanski <ski@mediamatters.org> Cc: freebsd-stable@freebsd.org, Lukas Ertl <le@FreeBSD.org> Subject: Re: gvinum/vinum on 6.0 Message-ID: <20060111125625.GL63938@pcwin002.win.tue.nl> In-Reply-To: <3657.68.49.189.193.1136980714.squirrel@68.49.189.193> References: <2178.68.49.189.193.1136950709.squirrel@68.49.189.193> <20060111064349.GJ63938@pcwin002.win.tue.nl> <3657.68.49.189.193.1136980714.squirrel@68.49.189.193>
next in thread | previous in thread | raw e-mail | index | archive | help
--7uYPyRQQ5N0D02nI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 11, 2006 at 06:58:34AM -0500, Brian Szymanski wrote: > Stijn, thanks for your help, I'm getting closer... Great! > > > But most importantly, gvinum configuration (at least for a raid-5 ple= x) > > > still doesn't persist across a reboot :( > > > > That's a bug; I think it might be related to compiling gvinum in the > > kernel > > as opposed to loading it from /boot/loader.conf. I also think there is a > > fix already commited to 6-STABLE. >=20 > Hmm, I upgraded to 6-STABLE and I'm still having the problem. >=20 > Here's basically how it happens: > gvinum create /etc/vinum.cnf > newfs /dev/gvinum/VOLUME > mount /dev/gvinum/VOLUME /mnt > #screw with /mnt, everything works and is happy, yay! > reboot >=20 > At this point I call "gvinum l" (which loads geom_vinum.ko) by hand (after > the reboot). My configuration mostly seems to persist - except or the > "drives" section... Ah ok. Hmm. Lukas will need to look at the initialization code path again I think. Sounds like some random pointer is being used somewhere. > Would I have better luck compiling gvinum into the kernel instead of > loading the module? What do other folks who have successful config's do? I use a third method: load geom_vinum.ko in /boot/loader.conf: [stijn@sandcat] <~> cat /boot/loader.conf | grep geom_vinum geom_vinum_load=3D"YES" But maybe those lost configurations have something to do with disks/controllers as well? Mine are Promise Ultra133 with Maxtor 200/250G drives, as well as an internal IDE chipset with Maxtor 120G drives. In any case, that's really an area that I'm unable to help you with, it all depends on a lot of GEOM internal stuff that I don't understand (yet). HTH, --Stijn --=20 > Thus again, we have succesfully proven that I cannot read minds. It doesn't help. Almost all you ever get is "This mind intentionally left blank." -- Steve VanDevender, alt.sysadmin.recovery --7uYPyRQQ5N0D02nI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDxQB5Y3r/tLQmfWcRAjv2AJ0Uv91L1wD+vQ2DWIizLqEMYg9nXQCglOBQ n/UdF6ok74BD9KOBqNCpnQQ= =sokK -----END PGP SIGNATURE----- --7uYPyRQQ5N0D02nI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060111125625.GL63938>