Date: Sat, 27 Sep 2003 11:04:05 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: David Gilbert <dgilbert@dclg.ca> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: recent changes prohibit vinum swap. Message-ID: <20030927013405.GY16008@wantadilla.lemis.com> In-Reply-To: <16244.52141.653633.965105@canoe.dclg.ca> References: <16244.40636.428865.644209@canoe.dclg.ca> <Pine.NEB.3.96L.1030926180831.59608A-100000@fledge.watson.org> <16244.52141.653633.965105@canoe.dclg.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--GXk5ufetu984H6pr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Friday, 26 September 2003 at 19:28:45 -0400, David Gilbert wrote: >>>>>> "Robert" =3D=3D Robert Watson <rwatson@freebsd.org> writes: > > Robert> On Fri, 26 Sep 2003, David Gilbert wrote: > >>> Recent changes to -CURRENT prohibit vinum swap: >>> >>> [1:6:306]root@mu:~> swapon /dev/vinum/swapmu swapon: >>> /dev/vinum/swapmu: Operation not supported by device > > Robert> In order to support swapping, Vinum will need to be modified > Robert> to use struct disk and the disk(9) API, rather than exposing > Robert> its storage devices directly via struct cdevsw and > Robert> make_dev(9). I.e., Vinum probably needs to start approaching > Robert> things as "disks" rather than "devices", a distinction that's > Robert> becoming more mature in -CURRENT. > >>> From a quick read of vinumconfig.c, I'm guessing this wouldn't be >>> hard to > Robert> implement. Some subset of struct sd, struct plex, and struct > Robert> volume will need to start holding a struct disk instance which > Robert> would be passed to disk_create() instead of a call to > Robert> make_dev(). Much of the remainder will just consist of a bit > Robert> of tweaking to make Vinum extract its data from > bp-> bio_disk->d_drv1 instead of bp->b_dev, replacing the ioctl dev_t > Robert> argument with a disk argument, etc. > > Is this something that someone can help me with quickly, or should I > downgrade the machine until it's been done?=20 Don't hold your breath. This will probably happen in the course of migrating Vinum functionality to GEOM. > Is there a quick hack to make it work for now? None that I know of. > If I must downgrade, what date would be appropriate? Sorry, I can't help there. Maybe phk can give you some indication. > Robert> I also noticed that the vinum commandline tool is a bit > Robert> devfs-unfriendly, or at least, it gets pretty verbose about > Robert> how all the files/directories it wants to create are already > Robert> present. It could be that a test for devfs conditionally > Robert> causing a test for EEXIST would go a long way in muffling the > Robert> somewhat loud complaining :-). > > Well... vinum is fragile in a whole bunch of ways. vinum rm often > leaves things in an inconsistant state. I almost always reboot now > after using it. vinum rename doesn't change the devfs vinum directory > ... which then also requires a reboot to correct. Hmm. That's another one to look at. > Another thing that's very fragile is resetconfig. It blanks memory, > but not disk. It should do. It leaves the device names, though. That's arguably a bug. Greg -- See complete headers for address and phone numbers. NOTE: Due to the currently active Microsoft-based worms, I am limiting all incoming mail to 131,072 bytes. This is enough for normal mail, but not for large attachments. Please send these as URLs. --GXk5ufetu984H6pr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/dOkNIubykFB6QiMRAm7+AJ49D+PFeXI+30orYhf8bi1jPPqiNwCfXCa8 8hcnA/0cjxUy6OiuFdK96V8= =CZRe -----END PGP SIGNATURE----- --GXk5ufetu984H6pr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030927013405.GY16008>