Date: Thu, 24 Aug 2006 14:59:13 +0200 From: Ulf Lilleengen <lulf@stud.ntnu.no> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-geom@freebsd.org Subject: Re: gvinum drivegroups and concat command Message-ID: <20060824125913.GB9677@stud.ntnu.no> In-Reply-To: <44ED9343.20402@centtech.com> References: <20060814073128.GA27499@stud.ntnu.no> <44ED9343.20402@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On tor, aug 24, 2006 at 06:53:39 -0500, Eric Anderson wrote: > On 08/14/06 02:31, Ulf Lilleengen wrote: > >Hi, > > > >I'm doing work on gvinum these days, and I've implemented a possibility = of > >drivegroups. It is possible to add drives to group at creation, but it= =20 > >will also > >be possible to add drives to groups afterwards. The advantage with=20 > >drivegroups > >are not very big right now, but I've started to work on the first comman= d=20 > >that > >will take utilization of drivegroups. > > > >The concat command creates a concatenated volume, and from old vinum, it= =20 > >uses > >drives as parameter. With drivegroups one can now still specify drives, = or > >groups or you don't even have to specify anything but the size, as gvinu= m=20 > >then > >will use the default drivegroup and create a volume for you there. > > > >This is how i think the concat command should be like: > > - if name not specified, use drivegroup-volnum (maybe=20 > > somethingelse) > > - size must be specified, or maybe a "fill drives/group" argumen= t? > > - if group specified, it tries to create subdisks on all drives = in=20 > > the > > drivegroup. > > - if drivegroup not specified, and neither drives; use > > defaultdrivegroup. > > - if drives specified, use them. overrides drivegroups. > > > >The general usage will be: > >concat [-f] [-n name] [-v] [-g group] [drives] > > > >Further advantages with drivegroups can be the mirror and stripe command= s,=20 > >as > >well as the possibility to move drivegroups between different machines a= nd=20 > >group > >your drives into logical collections. There will be more on this later. > > > >If anyone have any suggestions, I would like to hear it, as I'm starting= on > >implementing these commands now and think it's very important that it's= =20 > >being > >done right. If I have overlooked anything, feel free to comment. Other > >improvements in gvinum is mentioned in the lastest status report. > > >=20 > Will you also be able to remove/move drives from drivegroups? >=20 > This sounds like a neat feature. >=20 Yes. There are a lot of possibilities in drivegroups. It's inspired a bit f= rom diskgroups in the veritas vm. The concept is very similar, but veritas vm w= orks a bit different from vinum so not all features of veritas diskgroups will be = much of a use in gvinum. I named it drivegroups simply because we use drives, not disks in gvinum. There are some administrator papers on veritas which shows what can be done= with them: http://docs.sun.com/app/docs/coll/VERITAS_SF_4_0 The most relevant part is in the VERITAS Volume Manager 4.0 Administrator's Guide, which shows what diskgroups can be used for.=20 --=20 Mvh Ulf Lilleengen --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFE7aKhCILg8nMIdCURAlp3AJ9LRHrK2wsZ/cYla+vZgmgCCsvY/ACffMcv /WE4dRycGg5LIApK3tQMzTA= =uwb4 -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060824125913.GB9677>