From grog@lemis.com Thu May 22 12:52:36 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id 8F6BD99E31 for ; Thu, 22 May 2003 12:52:34 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2470451A94; Thu, 22 May 2003 12:52:35 +0930 (CST) Delivered-To: grog@lemis.com Received: from openbsd.cs.colorado.edu (openbsd.cs.colorado.edu [128.138.192.83]) by wantadilla.lemis.com (Postfix) with ESMTP id D32A951A6D for ; Mon, 19 May 2003 13:50:14 +0930 (CST) Received: from openbsd.org (localhost.cs.colorado.edu [127.0.0.1]) by openbsd.cs.colorado.edu (8.12.9/8.12.9) with ESMTP id h4J4Ir9m026810; Sun, 18 May 2003 22:19:04 -0600 (MDT) Received: from saga12.Stanford.EDU (saga12.Stanford.EDU [171.64.15.142]) by openbsd.cs.colorado.edu (8.12.9/8.12.9) with ESMTP id h4J4Enwr004670 for ; Sun, 18 May 2003 22:14:50 -0600 (MDT) Received: from localhost (tedu@localhost) by saga12.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4J4EidW006340 for ; Sun, 18 May 2003 21:14:44 -0700 (PDT) X-Authentication-Warning: saga12.Stanford.EDU: tedu owned process doing -bs Date: Sun, 18 May 2003 21:14:44 -0700 (PDT) From: Ted Unangst To: misc@openbsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: misc@openbsd.org Precedence: list X-Spam-Status: No, hits=-13.7 required=5.0 tests=BAYES_01,USER_AGENT_PINE,X_AUTH_WARNING,X_LOOP autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Resent-From: grog@lemis.com Resent-Date: Thu, 22 May 2003 12:52:35 +0930 Resent-To: Vinum Developers Mailing List Resent-Message-Id: <20030522032235.2470451A94@wantadilla.lemis.com> Subject: [Vinum-devel] vinum available Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Announcing the initial release of an OpenBSD port of Vinum. Vinum is a volume manager written by Greg Lemis for FreeBSD. It also does RAID 0, 1, and 5. This port is based on the NetBSD port by Atul Kabra, Ramsubramanyam and Shajid Thirvuthodi of Infosys Technologies, which Greg passed on to me. This is a preliminary effort. Some of the code may change due to cleanup, but I've tried to avoid making unnecessary changes to keep the code bases similar. This patch only covers i386. Other archs require tweaking conf.c and changing the ?MAJOR numbers in vinumvar.h. This is a problem that needs to be solved before integration. All you server types are encouraged to hammer on this. I don't have the hardware to really make this interesting; that's your job. There are two pieces to download and you need new -current to play. You will need to rebuild libutil, disklabel, and some other tools. Don't disklabel the volume, just newfs it. There is more documentation available concerning how to use vinum at www.vinumvm.org. sources for kernel driver and userland control program: http://www.stanford.edu/~tedu/vinum-openbsd.tgz kernel patch to integrate vinum: http://www.stanford.edu/~tedu/vinum-openbsd.diff -- "The laws in this city are clearly racist. All laws are racist. The law of gravity is racist." - M. Barry, Mayor of Washington, DC From grog@lemis.com Thu May 22 12:52:36 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id A98F299E3D for ; Thu, 22 May 2003 12:52:34 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2B59751A7C; Thu, 22 May 2003 12:52:35 +0930 (CST) Delivered-To: grog@lemis.com Received: from openbsd.cs.colorado.edu (openbsd.cs.colorado.edu [128.138.192.83]) by wantadilla.lemis.com (Postfix) with ESMTP id 25D3951A35 for ; Mon, 19 May 2003 15:29:34 +0930 (CST) Received: from openbsd.org (localhost.cs.colorado.edu [127.0.0.1]) by openbsd.cs.colorado.edu (8.12.9/8.12.9) with ESMTP id h4J5v49q017366; Sun, 18 May 2003 23:57:15 -0600 (MDT) Received: from saga19.Stanford.EDU (saga19.Stanford.EDU [171.64.15.149]) by openbsd.cs.colorado.edu (8.12.9/8.12.9) with ESMTP id h4J5rSwr011315 for ; Sun, 18 May 2003 23:53:28 -0600 (MDT) Received: from localhost (tedu@localhost) by saga19.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4J5rN7B021810 for ; Sun, 18 May 2003 22:53:23 -0700 (PDT) X-Authentication-Warning: saga19.Stanford.EDU: tedu owned process doing -bs Date: Sun, 18 May 2003 22:53:23 -0700 (PDT) From: Ted Unangst To: misc@openbsd.org In-Reply-To: <20030518235509.7ca634f3.lists@wyrmsoft.tzo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: misc@openbsd.org Precedence: list X-Spam-Status: No, hits=-32.3 required=5.0 tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REPLY_WITH_QUOTES,USER_AGENT_PINE,X_AUTH_WARNING,X_LOOP autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Resent-From: grog@lemis.com Resent-Date: Thu, 22 May 2003 12:52:35 +0930 Resent-To: Vinum Developers Mailing List Resent-Message-Id: <20030522032235.2B59751A7C@wantadilla.lemis.com> Subject: [Vinum-devel] Re: vinum available Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Sun, 18 May 2003, jason hord wrote: > not that i don't applaud the effort, but is there any real reason for > doing this? i just setup a couple of sparc64 machines with RAIDFrame > and have been perfectly happy with it. is there a technical reason why > i should be using vinum instead? it seemed unnecessarily complicated > to me. i'm interested to know since i have a server that will > (unfortunately) have to run FreeBSD on which i will probably be required > to use vinum since FreeBSD hasn't got RAIDFrame quite up to par yet. three main points. vinum supports volume management and resizing. the tools to resize FFS are not in our tree, but easy to come by and they work fine. there is no other option for volume management right now; i'm not about to write one when there's vinum free for the taking. just consider the RAID a bonus. i'm not a heavy raidframe user, but i've heard a few people complain about its performance, either low throughput or high cpu usage. word in the street is that vinum is better in this respect. it will be interesting to see numbers... vinum is 1/4 the size of raidframe. raidframe is 50000 lines of code; vinum is 12000. this is not significant by itself, but in terms of maintainence and understanding it matters. this also probably has something to do with the speed issue. comparing the man pages for vinum and raidctl, i can't say that raidctl is really that much simpler. both commands have many options. raidframe will not be going away, btw. vinum will become an alternative for those people who decide it's the better choice for them. -- "I am making this trip to Africa because Washington is an international city, just like Tokyo, Nigeria or Israel. As mayor, I am an international symbol. Can you deny that to Africa?" - M. Barry, Mayor of Washington, DC From grog@lemis.com Thu May 22 12:52:37 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id B089599E3E for ; Thu, 22 May 2003 12:52:34 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 316CA51A87; Thu, 22 May 2003 12:52:35 +0930 (CST) Delivered-To: grog@lemis.com Received: from openbsd.cs.colorado.edu (openbsd.cs.colorado.edu [128.138.192.83]) by wantadilla.lemis.com (Postfix) with ESMTP id 4CD6E51A35 for ; Mon, 19 May 2003 14:30:29 +0930 (CST) Received: from openbsd.org (localhost.cs.colorado.edu [127.0.0.1]) by openbsd.cs.colorado.edu (8.12.9/8.12.9) with ESMTP id h4J4xH9q022753; Sun, 18 May 2003 22:59:28 -0600 (MDT) Received: from hydra1.wyrmnet (pravus@ip68-109-33-154.lu.dl.cox.net [68.109.33.154]) by openbsd.cs.colorado.edu (8.12.9/8.12.9) with ESMTP id h4J4tBws004548 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sun, 18 May 2003 22:55:11 -0600 (MDT) Received: from leviathan.wyrmnet (leviathan.wyrmnet [10.0.0.50]) by hydra1.wyrmnet (8.12.9/8.12.9) with SMTP id h4J4t90G031972; Sun, 18 May 2003 23:55:10 -0500 (CDT) Date: Sun, 18 May 2003 23:55:09 -0500 From: jason hord To: Ted Unangst Cc: misc@openbsd.org Message-Id: <20030518235509.7ca634f3.lists@wyrmsoft.tzo.net> In-Reply-To: References: Organization: wyrm software X-Mailer: Sylpheed version 0.9.0 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Loop: misc@openbsd.org Precedence: list X-Spam-Status: No, hits=-26.0 required=5.0 tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,X_LOOP autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Resent-From: grog@lemis.com Resent-Date: Thu, 22 May 2003 12:52:35 +0930 Resent-To: Vinum Developers Mailing List Resent-Message-Id: <20030522032235.316CA51A87@wantadilla.lemis.com> Subject: [Vinum-devel] Re: vinum available Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: > Announcing the initial release of an OpenBSD port of Vinum. Vinum is > a volume manager written by Greg Lemis for FreeBSD. It also does RAID > 0, 1, and 5. This port is based on the NetBSD port by Atul Kabra, > Ramsubramanyam and Shajid Thirvuthodi of Infosys Technologies, which > Greg passed on to me. > > This is a preliminary effort. Some of the code may change due to > cleanup, but I've tried to avoid making unnecessary changes to keep > the code bases similar. This patch only covers i386. Other archs > require tweaking conf.c and changing the ?MAJOR numbers in vinumvar.h. > This is a problem > that needs to be solved before integration. not that i don't applaud the effort, but is there any real reason for doing this? i just setup a couple of sparc64 machines with RAIDFrame and have been perfectly happy with it. is there a technical reason why i should be using vinum instead? it seemed unnecessarily complicated to me. i'm interested to know since i have a server that will (unfortunately) have to run FreeBSD on which i will probably be required to use vinum since FreeBSD hasn't got RAIDFrame quite up to par yet. > All you server types are encouraged to hammer on this. I don't have > the hardware to really make this interesting; that's your job. There > are two pieces to download and you need new -current to play. You > will need to rebuild libutil, disklabel, and some other tools. Don't > disklabel the volume, just newfs it. > There is more documentation available concerning how to use vinum at > www.vinumvm.org. i wish i could... but i have an incompatible SCSI HBA. > sources for kernel driver and userland control program: > http://www.stanford.edu/~tedu/vinum-openbsd.tgz > kernel patch to integrate vinum: > http://www.stanford.edu/~tedu/vinum-openbsd.diff again, i applaud the effort if for no other reason than offering the userbase more options. thank-you. -- jason hord From tedu@stanford.edu Thu May 22 16:37:51 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from saga20.Stanford.EDU (saga20.Stanford.EDU [171.64.15.150]) by www.auug.org.au (Postfix) with ESMTP id D0C3D99E35 for ; Thu, 22 May 2003 16:37:50 +0930 (CST) Received: from localhost (tedu@localhost) by saga20.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4M77pjB017113 for ; Thu, 22 May 2003 00:07:51 -0700 (PDT) X-Authentication-Warning: saga20.Stanford.EDU: tedu owned process doing -bs Date: Thu, 22 May 2003 00:07:51 -0700 (PDT) From: Ted Unangst To: Vinum Developers Mailing List Subject: Re: [Vinum-devel] vinum available In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Sun, 18 May 2003, Ted Unangst wrote: > bases similar. This patch only covers i386. Other archs require tweaking > conf.c and changing the ?MAJOR numbers in vinumvar.h. This is a problem > that needs to be solved before integration. I need to ask, have you or anyone tried running vinum on sparc64? One of the shortcomings of both the 32 and 64 bit sparc ports is incomplete disklabels. They cannot define other file system types apparently, so vinum's strict insistence on fs type "vinum" will prevent it from working there. This is the reason ccd and raidframe accept ffs partitions. Perhaps freebsd has some other means of dealing with this? -- "What right does Congress have to go around making laws just because they deem it necessary?" - M. Barry, Mayor of Washington, DC From j@uriah.heep.sax.de Thu May 22 17:20:09 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by www.auug.org.au (Postfix) with ESMTP id AEAEC99E6A for ; Thu, 22 May 2003 17:20:06 +0930 (CST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id JAA04833 for vinum-devel@auug.org.au; Thu, 22 May 2003 09:50:06 +0200 (CEST) Received: from uriah.heep.sax.de (localhost.heep.sax.de [127.0.0.1]) by uriah.heep.sax.de (8.12.9/8.12.6) with ESMTP id h4M7jOJo086292 for ; Thu, 22 May 2003 09:45:24 +0200 (MET DST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.12.9/8.12.6/Submit) id h4M7jNaU086291 for vinum-devel@auug.org.au; Thu, 22 May 2003 09:45:23 +0200 (MET DST) (envelope-from j) Date: Thu, 22 May 2003 09:45:23 +0200 From: Joerg Wunsch To: Vinum Developers Mailing List Subject: Re: [Vinum-devel] vinum available Message-ID: <20030522094523.A86115@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from tedu@stanford.edu on Thu, May 22, 2003 at 12:07:51AM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Spam-Status: No, hits=-32.5 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT version=2.53 X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: As Ted Unangst wrote: > ... They cannot define other file system types apparently, > so vinum's strict insistence on fs type "vinum" will prevent it from > working there. This is the reason ccd and raidframe accept ffs > partitions. Vinum no longer insists on it. The IMHO only thing that currently depends on it is that disklabel(8) only accepts overlapping partitions if the overlapped one is either `c' or of type `vinum' since this is used to provide an `a' alias partition for root@vinum. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From grog@lemis.com Thu May 22 17:17:31 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id E628D99E6A for ; Thu, 22 May 2003 17:17:29 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 690F1527A8; Thu, 22 May 2003 17:17:30 +0930 (CST) Date: Thu, 22 May 2003 17:17:30 +0930 From: Greg 'groggy' Lehey To: Ted Unangst Cc: Vinum Developers Mailing List Message-ID: <20030522074730.GP68593@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="e2bLSPRkEYxxSNev" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Subject: [Vinum-devel] Vinum on SPARC64 (was: vinum available) Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --e2bLSPRkEYxxSNev Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thursday, 22 May 2003 at 0:07:51 -0700, Ted Unangst wrote: > On Sun, 18 May 2003, Ted Unangst wrote: > >> bases similar. This patch only covers i386. Other archs require tweaki= ng >> conf.c and changing the ?MAJOR numbers in vinumvar.h. This is a problem >> that needs to be solved before integration. > > I need to ask, have you or anyone tried running vinum on sparc64?=20 Not I personally, but I know that Harti Brandt has done so. He's on this list, so I hope you'll hear from him. > One of the shortcomings of both the 32 and 64 bit sparc ports is > incomplete disklabels. They cannot define other file system types > apparently, so vinum's strict insistence on fs type "vinum" will > prevent it from working there. This is the reason ccd and raidframe > accept ffs partitions. Perhaps freebsd has some other means of > dealing with this? I've puzzled over this myself. I suspect that there's something untidy going on behind the scenes. Maybe Harti can explain. Greg -- See complete headers for address and phone numbers --e2bLSPRkEYxxSNev Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+zICSIubykFB6QiMRAhIfAJ0TfCvGfvCtkBoNL/NSCspSxgnXOACeMmMh i1YVv4AxL0qPhIaRd/E7Jsw= =8Dx9 -----END PGP SIGNATURE----- --e2bLSPRkEYxxSNev-- From brandt@fokus.fraunhofer.de Thu May 22 22:39:38 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by www.auug.org.au (Postfix) with ESMTP id 4930499E6C; Thu, 22 May 2003 22:39:35 +0930 (CST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with ESMTP id h4MD9YE11106; Thu, 22 May 2003 15:09:34 +0200 (MEST) Date: Thu, 22 May 2003 15:09:34 +0200 (CEST) From: Harti Brandt To: "Greg 'groggy' Lehey" Cc: Ted Unangst , Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) In-Reply-To: <20030522074730.GP68593@wantadilla.lemis.com> Message-ID: <20030522150000.J647@beagle.fokus.fraunhofer.de> References: <20030522074730.GP68593@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Thu, 22 May 2003, Greg 'groggy' Lehey wrote: GgL>On Thursday, 22 May 2003 at 0:07:51 -0700, Ted Unangst wrote: GgL>> On Sun, 18 May 2003, Ted Unangst wrote: GgL>> GgL>>> bases similar. This patch only covers i386. Other archs require tweaking GgL>>> conf.c and changing the ?MAJOR numbers in vinumvar.h. This is a problem GgL>>> that needs to be solved before integration. GgL>> GgL>> I need to ask, have you or anyone tried running vinum on sparc64? GgL> GgL>Not I personally, but I know that Harti Brandt has done so. He's on GgL>this list, so I hope you'll hear from him. It runs just fine on my Ultra10. I updated today to the current -current after 35 days uptime. This thing serves my /usr/local via an ATM link from a vinum partition and appears to be faster than a 500k$ auspex (at least for the limited number of users I have). GgL>> One of the shortcomings of both the 32 and 64 bit sparc ports is GgL>> incomplete disklabels. They cannot define other file system types GgL>> apparently, so vinum's strict insistence on fs type "vinum" will GgL>> prevent it from working there. This is the reason ccd and raidframe GgL>> accept ffs partitions. Perhaps freebsd has some other means of GgL>> dealing with this? GgL> GgL>I've puzzled over this myself. I suspect that there's something GgL>untidy going on behind the scenes. Maybe Harti can explain. I did not investigate further, but I had to go through some iterations to first get vinum recognize the partitions. I labeled them through sysinstall. But then vinum did not like the type of the partitions and refused to use them. After I did a newfs on the partitions vinum suddenly liked them and everything was fine. Can't really say, what the problem was/is. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org From tedu@stanford.edu Thu May 29 07:49:00 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from saga15.Stanford.EDU (saga15.Stanford.EDU [171.64.15.145]) by www.auug.org.au (Postfix) with ESMTP id 1B72B99EA9 for ; Thu, 29 May 2003 07:48:59 +0930 (CST) Received: from localhost (tedu@localhost) by saga15.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4SMIvFm014194 for ; Wed, 28 May 2003 15:18:57 -0700 (PDT) X-Authentication-Warning: saga15.Stanford.EDU: tedu owned process doing -bs Date: Wed, 28 May 2003 15:18:57 -0700 (PDT) From: Ted Unangst To: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) In-Reply-To: <20030522150000.J647@beagle.fokus.fraunhofer.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Thu, 22 May 2003, Harti Brandt wrote: > I did not investigate further, but I had to go through some iterations to > first get vinum recognize the partitions. I labeled them through > sysinstall. But then vinum did not like the type of the partitions and > refused to use them. After I did a newfs on the partitions vinum suddenly > liked them and everything was fine. Can't really say, what the problem > was/is. what's your disklabel look like now? are the vinum major numbers the same for all archs? this appears to be a problem atm, because i'm not keen on creating gaping holes for archs with few majors. what i think i will do is create /dev/vinum/control in MAKEDEV, and teach vinum(8) to read the major number. this might involve creating a dummy control block device, so that vinum(8) knows what number to use for block devices, too. was this solved any other way for freebsd? -- "I promise you a police car on every sidewalk." - M. Barry, Mayor of Washington, DC From grog@lemis.com Thu May 29 13:51:04 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id E2EBB99EAC for ; Thu, 29 May 2003 13:51:02 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id CFF92527A6; Thu, 29 May 2003 13:51:00 +0930 (CST) Date: Thu, 29 May 2003 13:51:00 +0930 From: Greg 'groggy' Lehey To: Ted Unangst Cc: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) Message-ID: <20030529042100.GA20321@wantadilla.lemis.com> References: <20030522150000.J647@beagle.fokus.fraunhofer.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wednesday, 28 May 2003 at 15:18:57 -0700, Ted Unangst wrote: > On Thu, 22 May 2003, Harti Brandt wrote: > >> I did not investigate further, but I had to go through some iterations to >> first get vinum recognize the partitions. I labeled them through >> sysinstall. But then vinum did not like the type of the partitions and >> refused to use them. After I did a newfs on the partitions vinum suddenly >> liked them and everything was fine. Can't really say, what the problem >> was/is. > > what's your disklabel look like now? > are the vinum major numbers the same for all archs?=20 No. > this appears to be a problem atm, because i'm not keen on creating > gaping holes for archs with few majors. I don't see any need for the major numbers to be the same. About the only issue is the man page, which I'm currently rewriting. > what i think i will do is create /dev/vinum/control in MAKEDEV, and > teach vinum(8) to read the major number. This shouldn't be necessary. vinum(8) creates these nodes itself. Have you had difficulties in this area? The initialization code of /usr/src/sbin/vinum/v.c attempts to open the super device. If it fails with ENOENT, it calls make_devices(), which creates all required device nodes: if (mknod(VINUM_SUPERDEV_NAME, S_IRUSR | S_IWUSR | S_IFCHR, /* user only */ makedev(VINUM_CDEV_MAJOR, VINUM_SUPERDEV_VOL)) < 0) fprintf(stderr, "Can't create %s: %s\n", VINUM_SUPERDEV_NAME, strerror(err= no)); superdev =3D open(VINUM_SUPERDEV_NAME, O_RDWR); /* open the super d= evice */ VINUM_CDEV_MAJOR is defined in /usr/src/sys/dev/vinum/vinumvar.h. > this might involve creating a dummy control block device, so that > vinum(8) knows what number to use for block devices, too. was this > solved any other way for freebsd? FreeBSD release 5 no longer has block devices, but I thought the code I gave you still refers to them. If not, I'll take a look and get you the correct version. Greg -- See complete headers for address and phone numbers --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+1YqsIubykFB6QiMRApEVAJwPnJyVz/EU3w/9PzFZabAZzdcKlQCgsiYx AllTGuwphpKYgM6oubGx2ms= =Lhe8 -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From tedu@stanford.edu Thu May 29 17:27:03 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from saga15.Stanford.EDU (saga15.Stanford.EDU [171.64.15.145]) by www.auug.org.au (Postfix) with ESMTP id 8973599EAB; Thu, 29 May 2003 17:27:02 +0930 (CST) Received: from localhost (tedu@localhost) by saga15.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4T7v1Sg003579; Thu, 29 May 2003 00:57:01 -0700 (PDT) X-Authentication-Warning: saga15.Stanford.EDU: tedu owned process doing -bs Date: Thu, 29 May 2003 00:57:01 -0700 (PDT) From: Ted Unangst To: "Greg 'groggy' Lehey" Cc: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) In-Reply-To: <20030529042100.GA20321@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Thu, 29 May 2003, Greg 'groggy' Lehey wrote: > > what i think i will do is create /dev/vinum/control in MAKEDEV, and > > teach vinum(8) to read the major number. > > This shouldn't be necessary. vinum(8) creates these nodes itself. > Have you had difficulties in this area? > > The initialization code of /usr/src/sbin/vinum/v.c attempts to open > the super device. If it fails with ENOENT, it calls make_devices(), > which creates all required device nodes: > > if (mknod(VINUM_SUPERDEV_NAME, > S_IRUSR | S_IWUSR | S_IFCHR, /* user only */ > makedev(VINUM_CDEV_MAJOR, VINUM_SUPERDEV_VOL)) < 0) > fprintf(stderr, "Can't create %s: %s\n", VINUM_SUPERDEV_NAME, strerror(errno)); > > superdev = open(VINUM_SUPERDEV_NAME, O_RDWR); /* open the super device */ > > VINUM_CDEV_MAJOR is defined in /usr/src/sys/dev/vinum/vinumvar.h. herein lies the problem. I will need to make a #ifdef for each arch and define it to a different number. This is not a difficult problem; however, it is not standard practice. All other devices are major agnostic. Without a running FreeBSD system, it's hard for me to know how FreeBSD picks different majors (seems like it always uses 91). It appears every device picks its own major, and registers it with the kernel at attachment. Meaning they are the same for all archs, no? OpenBSD still places majors and ?devsw in conf.c by arch, meaning a device has no control over the major it is assigned. vinum represents the first program which will depend on knowing the correct number, and not just the name, of an entry in /dev. But this is not a technical problem by any means. On the bright side, vinum may be incorporated soon, once I receive a positive report from somebody stressing it under production like conditions. -- "I am a great mayor; I am an upstanding Christian man; I am an intelligent man; I am a deeply educated man; I am a humble man." - M. Barry, Mayor of Washington, DC From grog@lemis.com Thu May 29 17:42:55 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id 1F66C99EAD for ; Thu, 29 May 2003 17:42:53 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id A986E527A7; Thu, 29 May 2003 17:42:48 +0930 (CST) Date: Thu, 29 May 2003 17:42:48 +0930 From: Greg 'groggy' Lehey To: Ted Unangst Cc: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) Message-ID: <20030529081248.GW20321@wantadilla.lemis.com> References: <20030529042100.GA20321@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Zqkt5x/gGOIVPcL0" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --Zqkt5x/gGOIVPcL0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 29 May 2003 at 0:57:01 -0700, Ted Unangst wrote: > On Thu, 29 May 2003, Greg 'groggy' Lehey wrote: > >>> what i think i will do is create /dev/vinum/control in MAKEDEV, and >>> teach vinum(8) to read the major number. >> >> This shouldn't be necessary. vinum(8) creates these nodes itself. >> Have you had difficulties in this area? >> >> The initialization code of /usr/src/sbin/vinum/v.c attempts to open >> the super device. If it fails with ENOENT, it calls make_devices(), >> which creates all required device nodes: >> >> if (mknod(VINUM_SUPERDEV_NAME, >> S_IRUSR | S_IWUSR | S_IFCHR, /* user only */ >> makedev(VINUM_CDEV_MAJOR, VINUM_SUPERDEV_VOL)) < 0) >> fprintf(stderr, "Can't create %s: %s\n", VINUM_SUPERDEV_NAME, strerror(errno)); >> >> superdev = open(VINUM_SUPERDEV_NAME, O_RDWR); /* open the super device */ >> >> VINUM_CDEV_MAJOR is defined in /usr/src/sys/dev/vinum/vinumvar.h. > > herein lies the problem. I will need to make a #ifdef for each arch and > define it to a different number. This is not a difficult problem; > however, it is not standard practice. All other devices are major > agnostic. Ah. I misunderstood the question. > Without a running FreeBSD system, it's hard for me to know how > FreeBSD picks different majors (seems like it always uses 91). Yes. I'm pretty sure that FreeBSD used the same major numbers for each architecture, with holes in some cases. > It appears every device picks its own major, and registers it with > the kernel at attachment. Meaning they are the same for all archs, > no? Yes. The numbers are defined in /usr/src/sys/conf/majors. I see that NetBSD has separate major numbers for each architecture, which shouldn't be a problem. I've spent a bit of time looking through the OpenBSD source tree, but I can't see how major numbers are allocated. Can you explain? > OpenBSD still places majors and ?devsw in conf.c by arch, meaning a > device has no control over the major it is assigned. vinum > represents the first program which will depend on knowing the > correct number, and not just the name, of an entry in /dev. But > this is not a technical problem by any means. Hmm. This is a chicken and egg problem. I was going to say "It should be relatively simple to implement an ioctl to return the major number", but that's nonsense, of course. Maybe the MAKEDEV kludge is a good first step. Is there a danger that the major number will wander on the same architecture from one release to the next? If you create the control device, that should be enough for vinum(8) to look at and extract the major number, of course. > On the bright side, vinum may be incorporated soon, once I receive a > positive report from somebody stressing it under production like > conditions. Sounds good. I've found and fixed a few bugs in the last few weeks. I'll take a look at the code you sent me and send you some diffs. If you want, I can give you the master tree, but I'm not very happy with the way I'm handling it yet. Greg -- See complete headers for address and phone numbers --Zqkt5x/gGOIVPcL0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+1cEAIubykFB6QiMRAn1oAKCTt2kEcXERinQzF8AWy5NjaQNawwCeOMKF mtwkNw5ldhpJFvDgrZoib1s= =T3nJ -----END PGP SIGNATURE----- --Zqkt5x/gGOIVPcL0-- From tedu@stanford.edu Fri May 30 06:55:16 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from saga3.Stanford.EDU (saga3.Stanford.EDU [171.64.15.133]) by www.auug.org.au (Postfix) with ESMTP id C9B8399EBB; Fri, 30 May 2003 06:55:14 +0930 (CST) Received: from localhost (tedu@localhost) by saga3.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4TLP96N008426; Thu, 29 May 2003 14:25:09 -0700 (PDT) X-Authentication-Warning: saga3.Stanford.EDU: tedu owned process doing -bs Date: Thu, 29 May 2003 14:25:09 -0700 (PDT) From: Ted Unangst To: "Greg 'groggy' Lehey" Cc: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) In-Reply-To: <20030529081248.GW20321@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Thu, 29 May 2003, Greg 'groggy' Lehey wrote: > Yes. The numbers are defined in /usr/src/sys/conf/majors. I see that > NetBSD has separate major numbers for each architecture, which > shouldn't be a problem. I've spent a bit of time looking through the > OpenBSD source tree, but I can't see how major numbers are allocated. > Can you explain? There is a static (not changing) array in arch/i386/i386/conf.c. Major number is implicit by location in the array. This is just historical BSD behavior I believe, Free/Net have both removed this file and generate it with config from a majors textfile. So devices aren't really assigned a major, they just happen to get whatever the next slot in the array is, which varies widely by arch. There are holes where devices were removed, however it's not good to introduce new holes. Then it's hard to tell whether it's safe to place a new device in the hole or not. > > OpenBSD still places majors and ?devsw in conf.c by arch, meaning a > > device has no control over the major it is assigned. vinum > > represents the first program which will depend on knowing the > > correct number, and not just the name, of an entry in /dev. But > > this is not a technical problem by any means. > > Hmm. This is a chicken and egg problem. I was going to say "It > should be relatively simple to implement an ioctl to return the major > number", but that's nonsense, of course. Maybe the MAKEDEV kludge is > a good first step. Is there a danger that the major number will > wander on the same architecture from one release to the next? No, I don't think it's ever changed between releases. I basically wanted to confirm that FreeBSD uses the same major for each arch. Now that I see that's the case, I'll just workaround it for OpenBSD. > Sounds good. I've found and fixed a few bugs in the last few weeks. > I'll take a look at the code you sent me and send you some diffs. If > you want, I can give you the master tree, but I'm not very happy with > the way I'm handling it yet. I don't have much time to fuss with this now, but after the commit, I would like to help merge sources to the extent that's possible. -- "I promise you a police car on every sidewalk." - M. Barry, Mayor of Washington, DC From brandt@fokus.fraunhofer.de Mon Jun 2 22:27:31 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by www.auug.org.au (Postfix) with ESMTP id 5324F976DF for ; Mon, 2 Jun 2003 22:27:29 +0930 (CST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with ESMTP id h52CvLv06819; Mon, 2 Jun 2003 14:57:21 +0200 (MEST) Date: Mon, 2 Jun 2003 14:57:20 +0200 (CEST) From: Harti Brandt To: Ted Unangst Cc: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Vinum on SPARC64 (was: vinum available) In-Reply-To: Message-ID: <20030602144832.C609@beagle.fokus.fraunhofer.de> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Wed, 28 May 2003, Ted Unangst wrote: TU>On Thu, 22 May 2003, Harti Brandt wrote: TU> TU>> I did not investigate further, but I had to go through some iterations to TU>> first get vinum recognize the partitions. I labeled them through TU>> sysinstall. But then vinum did not like the type of the partitions and TU>> refused to use them. After I did a newfs on the partitions vinum suddenly TU>> liked them and everything was fine. Can't really say, what the problem TU>> was/is. TU> TU>what's your disklabel look like now? To be honest, I'm now a little bit lost in these sunlabel/disklabel/bsdlabel mazes. disklabel da0 returns: # /dev/da0: text: FreeBSD17G cyl 2229 alt 2 hd 255 sec 63 bytes/sectors: 512 sectors/cylinder: 16065 sectors/unit: 35808885 8 partitions: # # Size is in sectors, use %dK, %dM or %dG to specify in kilobytes, # megabytes or gigabytes respectively, or '*' to specify rest of disk. # Offset is in cylinders, use '*' to calculate offsets automatically. # # size offset # ---------- ---------- c: 35808885 0 d: 35808885 0 This seems to be a Sun label. As far as I remember I used sysinstall to create it, because we had no sunlabel tool at that time. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org From grog@lemis.com Sat Aug 23 11:02:07 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from wantadilla.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id CB1339A43A for ; Sat, 23 Aug 2003 11:02:06 +0930 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 942E5526BF; Sat, 23 Aug 2003 11:02:04 +0930 (CST) Date: Sat, 23 Aug 2003 11:02:04 +0930 From: Greg 'groggy' Lehey To: Vinum Developers Mailing List Message-ID: <20030823013204.GJ59976@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Tu8ztk+XgTAiG9Id" Content-Disposition: inline User-Agent: Mutt/1.4i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Subject: [Vinum-devel] Need somebody to MFC FreeBSD-CURRENT fixes into 4.9 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --Tu8ztk+XgTAiG9Id Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It's a couple of days before the code freeze for FreeBSD 4.9, and there are a number of bug fixes in the -CURRENT branch which I haven't merged into 4-STABLE. I won't make it before the deadline, either, which means (presumably) that they would never make it, since 4.9 will probably be the last version of FreeBSD 4. Does anybody out there have time to do it? You don't have to be a FreeBSD committer, as long as you can do the updates and marginal testing. I can then do the rest. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers --Tu8ztk+XgTAiG9Id Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/RsQUIubykFB6QiMRAhbXAJ0cLfrMVNFqaVgX7YYCJvHBZuvSwACbBvcT K+BsQNdzycSBwWfLjRxuWnk= =ZnbY -----END PGP SIGNATURE----- --Tu8ztk+XgTAiG9Id-- From marck@rinet.ru Sun Aug 24 20:24:30 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by www.auug.org.au (Postfix) with ESMTP id 1A7C89A3F0 for ; Sun, 24 Aug 2003 20:24:29 +0930 (CST) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.9/8.12.9) with ESMTP id h7OAsO4D007698; Sun, 24 Aug 2003 14:54:25 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 24 Aug 2003 14:54:24 +0400 (MSD) From: Dmitry Morozovsky To: "Greg 'groggy' Lehey" Cc: Vinum Developers Mailing List Subject: Re: [Vinum-devel] Need somebody to MFC FreeBSD-CURRENT fixes into 4.9 In-Reply-To: <20030823013204.GJ59976@wantadilla.lemis.com> Message-ID: <20030824145145.Q3959@woozle.rinet.ru> References: <20030823013204.GJ59976@wantadilla.lemis.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Sat, 23 Aug 2003, Greg 'groggy' Lehey wrote: GgL> It's a couple of days before the code freeze for FreeBSD 4.9, and GgL> there are a number of bug fixes in the -CURRENT branch which I haven't GgL> merged into 4-STABLE. I won't make it before the deadline, either, GgL> which means (presumably) that they would never make it, since 4.9 will GgL> probably be the last version of FreeBSD 4. GgL> GgL> Does anybody out there have time to do it? You don't have to be a GgL> FreeBSD committer, as long as you can do the updates and marginal GgL> testing. I can then do the rest. I'll be glad to test proposed patches; however, I'm rather limited in hardware base. Anyway, the more testers the better, ain't it? ;) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From Bob@VanValzah.Com Wed Aug 27 11:08:09 2003 Return-Path: Delivered-To: vinum-devel@auug.org.au Received: from Bastion.VanValzah.Com (Bastion.VanValzah.Com [64.81.228.180]) by www.auug.org.au (Postfix) with ESMTP id 9D5A79A468 for ; Wed, 27 Aug 2003 11:08:06 +0930 (CST) Received: from [10.168.60.10] (CoolDude.VanValzah.Com [10.168.60.10]) by Bastion.VanValzah.Com (8.12.8p1/8.12.8) with ESMTP id h7R1c3gP069863; Tue, 26 Aug 2003 20:38:03 -0500 (CDT) (envelope-from Bob@VanValzah.Com) From: Bob Van Valzah To: Vinum Developers Mailing List Cc: Kirk Strauser Content-Type: text/plain Message-Id: <1061948282.3894.14.camel@CoolDude.VanValzah.Com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 26 Aug 2003 20:38:03 -0500 Content-Transfer-Encoding: 7bit Subject: [Vinum-devel] Monitoring Vinum with Nagios Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: This is more of a Vinum admin issue than a developer issue, but I hope you'll excuse the slightly off-topic posting. I can't be the only guy who wanted a way to monitor Vinum for failures since SNMP has been on the Vinum Features Wish List for as long as I can remember. I've been using SNMP monitoring for a long time and recently started using Nagios as well. http://www.nagios.org/ I was very pleasantly surprised recently when I discovered that Kirk Strauser had developed a Nagios plugin that does exactly what I want. http://subwiki.honeypot.net/cgi-bin/view/Freebsd/CheckVinum Now my pager goes off shortly after any defective Vinum objects pop up. Very nice! Bob From jason@jason.id.au Fri Nov 14 18:18:30 2003 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from relay3.softcomca.com (relay3.softcomca.com [168.144.1.70]) by www.auug.org.au (Postfix) with ESMTP id 8DECD97701 for ; Fri, 14 Nov 2003 18:18:29 +1030 (CST) Received: from M2W035.mail2web.com ([168.144.251.140]) by relay3.softcomca.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 14 Nov 2003 02:48:28 -0500 Message-ID: <197180-220031151474828575@M2W035.mail2web.com> X-Priority: 3 Reply-To: jason@jason.id.au X-Originating-IP: 150.101.212.224 X-URL: http://mail2web.com/ From: "jason@jason.id.au" To: vinum-devel@auug.org.au Date: Fri, 14 Nov 2003 02:48:28 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 14 Nov 2003 07:48:28.0567 (UTC) FILETIME=[B120F270:01C3AA83] Subject: [Vinum-devel] vinnum recovering raid0 failed drive Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Hi, From the name of the mailing list I guess this may be only developer questions, although I am after some much needed assistance and have turned= to you people for some help=2E I am running freeBSD 4=2E8, and have 3 drives=2E One running the OS and t= he other 2 drives running raid0 with vinnum=2E The drive running the OS fail= ed, so I lost all my vinnum configuration=2E I am trying to remount the raid0 with no luch at all, and was wondering if= anyone could help me on the procedure to do this=2E It has become that urgent I am even willing to return a favour if I can=2E Below is the outpur of my drive=2E It appears my multiple attempts at try= ing to repair my stripe have added extra disks=2E Can anyone lend any much needed assistance? Thanks for your time=2E Jason # vinum l -r stripe V stripe State: down Plexes: 3 Size: 148 G= B P stripe=2Ep0 S State: faulty Subdisks: 2 Size: 148= GB P stripe=2Ep1 S State: faulty Subdisks: 2 Size: 148= GB P stripe=2Ep2 S State: faulty Subdisks: 2 Size: 148= GB S stripe=2Ep0=2Es0 State: crashed PO: 0 B Size: = 74 GB S stripe=2Ep0=2Es1 State: crashed PO: 256 kB Size: = 74 GB S stripe=2Ep1=2Es0 State: stale PO: 0 B Size: = 74 GB S stripe=2Ep1=2Es1 State: stale PO: 256 kB Size: = 74 GB S stripe=2Ep2=2Es0 State: stale PO: 0 B Size: = 74 GB S stripe=2Ep2=2Es1 State: stale PO: 256 kB Size: = 74 GB -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web=2Ecom/ =2E From Daryl.Tester@iocane.com.au Fri Nov 14 19:31:56 2003 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from gizmo09bw.bigpond.com (gizmo09bw.bigpond.com [144.140.70.19]) by www.auug.org.au (Postfix) with SMTP id 3F524976C7 for ; Fri, 14 Nov 2003 19:31:56 +1030 (CST) Received: (qmail 30093 invoked from network); 13 Nov 2003 08:00:32 -0000 Received: from unknown (HELO zen.testernet) (144.135.24.69) by gizmo09bw.bigpond.com with SMTP; 13 Nov 2003 08:00:32 -0000 Received: from 144.139.61.101 ([144.139.61.101]) by bwmam01.bigpond.com(MAM REL_3_3_2d 2/3331436); 14 Nov 2003 19:01:45 Received: from iocane.com.au (nipnyep [172.16.0.2]) by zen.testernet (8.12.6/8.12.6) with ESMTP id hAE8tACS022632; Fri, 14 Nov 2003 19:25:11 +1030 (CST) (envelope-from Daryl.Tester@iocane.com.au) Message-ID: <3FB4993D.E720F5E5@iocane.com.au> Date: Fri, 14 Nov 2003 19:28:37 +1030 From: Daryl Tester X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: jason@jason.id.au Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] vinnum recovering raid0 failed drive References: <197180-220031151474828575@M2W035.mail2web.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: "jason@jason.id.au" wrote: > I am running freeBSD 4.8, and have 3 drives. One running the OS and the > other 2 drives running raid0 with vinnum. The drive running the OS failed, > so I lost all my vinnum configuration. Well, I'm willing to be corrected on this, but I'm pretty certain that the vinum configuration is stored on the vinum drive itself, so unless you lost both drives your configuration should have been intact. > Below is the outpur of my drive. It appears my multiple attempts at trying > to repair my stripe have added extra disks. What's the output of "vinum list" show? -- Regards, Daryl Tester, Software Wrangler and Bit Herder, IOCANE Pty. Ltd. "AIX looks like it was implemented by a pretty smart space alien who heard Unix described to him by a different space alien, but they had to gesture a lot because their universal translators were broken." -- Joe Keane From grog@lemis.com Mon Nov 17 14:37:37 2003 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blackwater.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id C6409976D8 for ; Mon, 17 Nov 2003 14:37:35 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id BA18E511FA; Mon, 17 Nov 2003 14:37:33 +1030 (CST) Date: Mon, 17 Nov 2003 14:37:33 +1030 From: Greg 'groggy' Lehey To: "jason@jason.id.au" Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] vinnum recovering raid0 failed drive Message-ID: <20031117040733.GD32042@wantadilla.lemis.com> References: <197180-220031151474828575@M2W035.mail2web.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="e7WmlSfQJTtHfSol" Content-Disposition: inline In-Reply-To: <197180-220031151474828575@M2W035.mail2web.com> User-Agent: Mutt/1.4.1i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --e7WmlSfQJTtHfSol Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Friday, 14 November 2003 at 2:48:28 -0500, jason@jason.id.au wrote: > Hi, > From the name of the mailing list I guess this may be only developer > questions, although I am after some much needed assistance and have turned > to you people for some help. Yes, it's really for developer questions. This one would have been more appropriate on FreeBSD-questions, but let's look anyway. > I am running freeBSD 4.8, and have 3 drives. One running the OS and > the other 2 drives running raid0 with vinnum. The drive running the > OS failed, so I lost all my vinnum configuration. As Daryl has already noted, the configuration is stored on every Vinum drive, so you shouldn't have lost the configuration. > I am trying to remount the raid0 with no luch at all, and was wondering if > anyone could help me on the procedure to do this. It has become that > urgent I am even willing to return a favour if I can. > > Below is the outpur of my drive. It appears my multiple attempts at trying > to repair my stripe have added extra disks. > > V stripe State: down Plexes: 3 Size: 148 GB > P stripe.p0 S State: faulty Subdisks: 2 Size: 148 GB > P stripe.p1 S State: faulty Subdisks: 2 Size: 148 GB > P stripe.p2 S State: faulty Subdisks: 2 Size: 148 GB > S stripe.p0.s0 State: crashed PO: 0 B Size: 74 GB > S stripe.p0.s1 State: crashed PO: 256 kB Size: 74 GB > S stripe.p1.s0 State: stale PO: 0 B Size: 74 GB > S stripe.p1.s1 State: stale PO: 256 kB Size: 74 GB > S stripe.p2.s0 State: stale PO: 0 B Size: 74 GB > S stripe.p2.s1 State: stale PO: 256 kB Size: 74 GB Yes, this is a feature, not a bug. You shouldn't tell Vinum to add more plexes to an existing object. What does 'vinum dumpconfig' say? Greg -- See complete headers for address and phone numbers. --e7WmlSfQJTtHfSol Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/uEmFIubykFB6QiMRAvG5AJ4voHXvJQY1B4SCrAOGEPFZU6qdoACgsEOR 5VSurXC2h5lGNIkE3Ce+nRg= =hxni -----END PGP SIGNATURE----- --e7WmlSfQJTtHfSol-- From marck@rinet.ru Mon Nov 17 21:46:29 2003 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by www.auug.org.au (Postfix) with ESMTP id 9F8E8976CD; Mon, 17 Nov 2003 21:46:27 +1030 (CST) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.10/8.12.10) with ESMTP id hAHBGISD026029; Mon, 17 Nov 2003 14:16:18 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Mon, 17 Nov 2003 14:16:18 +0300 (MSK) From: Dmitry Morozovsky To: "Greg 'groggy' Lehey" Cc: "jason@jason.id.au" , vinum-devel@auug.org.au Subject: Re: [Vinum-devel] vinnum recovering raid0 failed drive In-Reply-To: <20031117040733.GD32042@wantadilla.lemis.com> Message-ID: <20031117140945.M25190@woozle.rinet.ru> References: <197180-220031151474828575@M2W035.mail2web.com> <20031117040733.GD32042@wantadilla.lemis.com> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Mon, 17 Nov 2003, Greg 'groggy' Lehey wrote: GgL> Yes, this is a feature, not a bug. You shouldn't tell Vinum to add GgL> more plexes to an existing object. Hmm. Why? For me, it seems the most logical way to get on-line backup: attach physical disk vinum read vinum attach vol.px vol vinum start vol.px (to bring plexes in-sync) vinum detach vol.px [here should be way to correctly remove physical drive with underlying objects, which i'm not aware of] physically detach disk BTW, Greg, could I ask you to look at kern/59303? Thanks in advance. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From vinum@achtung.com Fri Jan 9 17:15:56 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blotto.achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) by www.auug.org.au (Postfix) with ESMTP id 9C93997C55 for ; Fri, 9 Jan 2004 17:15:55 +1030 (CST) Received: from achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) (AUTH: LOGIN albert) by blotto.achtung.com with esmtp; Fri, 09 Jan 2004 14:46:51 +0800 Message-ID: <3FFE4E35.9040906@achtung.com> Date: Fri, 09 Jan 2004 14:46:13 +0800 From: Albert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vinum-devel@auug.org.au Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Vinum-devel] Vinum Install on FreeBSD 5.1 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: I had some problems installing Vinum, but got it going on the 6th try.. I miscounted (or rather, on one of them) forgot to subtract 16 from the offset.. and strange things happened, one of which was a kernel panic and an auto reboot.. Documentation is hairy at best, and I've read all that is available on it about 20 times, and still made mistakes. Hopefully, I'll find some time this coming week to write documentation based on my own experience of setting up Vinum. But once setup, it's fairly transparent. I'm doing bonnie++ tests on the box right now; I'll post my results. I have 2HD's running them RAID 1 Duplexed... HD1 = Seagate 40Gig 5400rpm. HD2 = IBM Deskstar 41Gig 7200rpm The system is on a scrapped Pentium II 350Mhz with only 64Megs of ram.. I'm going to run 5 (bonnie++) tests: HD1 raw (no vinum) HD2 raw (no vinum) HD1 vinum with HD2 down HD2 vinum with HD1 down HD vinum RAID 1 duplexed. Hopefully, I'll be able to finish all the tests and publish a reasonable result today or tomorrow. Albert From grog@lemis.com Fri Jan 9 17:25:36 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blackwater.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id 3B8E297705 for ; Fri, 9 Jan 2004 17:25:35 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 66DA15121A; Fri, 9 Jan 2004 17:25:33 +1030 (CST) Date: Fri, 9 Jan 2004 17:25:33 +1030 From: Greg 'groggy' Lehey To: Albert Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Vinum Install on FreeBSD 5.1 Message-ID: <20040109065533.GL7617@wantadilla.lemis.com> References: <3FFE4E35.9040906@achtung.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZnpN70eih+TtwZsO" Content-Disposition: inline In-Reply-To: <3FFE4E35.9040906@achtung.com> User-Agent: Mutt/1.4.1i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --ZnpN70eih+TtwZsO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Friday, 9 January 2004 at 14:46:13 +0800, Albert wrote: > I had some problems installing Vinum, but got it going on the 6th try.. > > I miscounted (or rather, on one of them) forgot to subtract 16 from the > offset.. and strange things happened, one of which was a kernel panic > and an auto reboot.. > > Documentation is hairy at best, and I've read all that is available on > it about 20 times, and still made mistakes. Hopefully, I'll find some > time this coming week to write documentation based on my own experience > of setting up Vinum. But once setup, it's fairly transparent. It would be good to understand which rough edges of the documentation caused you grief, particularly the chapter from "The Complete FreeBSD". > I'm doing bonnie++ tests on the box right now; I'll post my results. bonniee++ takes a lot of interpretation, and a large part of it doesn't deliver any useful information about the underlying storage devices. Try rawio. Greg -- See complete headers for address and phone numbers. --ZnpN70eih+TtwZsO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE//lBlIubykFB6QiMRAt8iAJ9XkM7z9V51sRnBhxz2Bs8mY9su4QCaAnTJ IzeDdMg7R6BFIZwyYjHx3hA= =AZlS -----END PGP SIGNATURE----- --ZnpN70eih+TtwZsO-- From vinum@achtung.com Fri Jan 9 18:56:34 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blotto.achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) by www.auug.org.au (Postfix) with ESMTP id AE3BC97B2E for ; Fri, 9 Jan 2004 18:56:25 +1030 (CST) Received: from achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) (AUTH: LOGIN albert) by blotto.achtung.com with esmtp; Fri, 09 Jan 2004 16:27:16 +0800 Message-ID: <3FFE65BC.8090005@achtung.com> Date: Fri, 09 Jan 2004 16:26:36 +0800 From: Albert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Vinum Install on FreeBSD 5.1 References: <3FFE4E35.9040906@achtung.com> <20040109065533.GL7617@wantadilla.lemis.com> In-Reply-To: <20040109065533.GL7617@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: I'll give RawIO a shot... I'm almost done with most of my Bonnie++ tests.. while it might be biased, on a system like a PII 350Mhz, and 64megs ram, it won't be because of the CPU speed! I'm writing some documentation about RAID 1, and arguments for RAID on software vs hardware as a cheap solution for reliability... If you get a chance, get a redhat 9 CD, and try an install.. You don't actually need to install redhat, just run through the menus of their integrated software raid install. That took me about 2 minutes, where Vinum took me about 5 hours... There's a lot going on as far as installing vinum that seems quite complex. Also, the vinum nomenclature is just aweful (I assume that which is gleamed from Veritas..) I'm hoping to maybe draw up interpretations.. for example, I get confused plex vs subdisk.. You have a HUGE amount of stuff not to get confused with; for example.. Harddrive (spindle) vs. Fdisk partition vs. Unix partition vs volume vs plex, vs subdisk.. Like I said before, I can probably assist on the documentation side, and give pointers and help there... Any other tests I should consider besides rawio? Albert From vinum@achtung.com Fri Jan 9 20:11:13 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blotto.achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) by www.auug.org.au (Postfix) with ESMTP id EA5F7976E3 for ; Fri, 9 Jan 2004 20:11:11 +1030 (CST) Received: from achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) (AUTH: LOGIN albert) by blotto.achtung.com with esmtp; Fri, 09 Jan 2004 17:42:09 +0800 Message-ID: <3FFE774A.4050407@achtung.com> Date: Fri, 09 Jan 2004 17:41:30 +0800 From: Albert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vinum-devel@auug.org.au Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Vinum-devel] Vinum Crash Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Well.. I should buy a lotto ticket today; I managed to crash vinum and freebsd about 12 times today... I had detached one of the plexes and now I can't reattach it! Any ideas? Actually, I'm a bit confused here.. My subdisk tmp.p0.s0 is up But my plex tmp.p0 is faulty and it says Subdisks: 0 Size: 0 So does this mean I want to attach my subdisk to the plex again? attach tmp.p0.s0 tmp.p0 Can't attach tmp.p0.s0 to tmp.p0 (smily face extended ascii character) (4) ??? and if I leave it as such (since my tmp.p1 as well as my tmp.p1.s0 is up) the kernel crashes, and forces a reboot. I have to boot into single user mode and not attach the /tmp directory.. ?? Albert From vinum@achtung.com Fri Jan 9 20:17:03 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blotto.achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) by www.auug.org.au (Postfix) with ESMTP id 5C9F597BDF for ; Fri, 9 Jan 2004 20:17:02 +1030 (CST) Received: from achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) (AUTH: LOGIN albert) by blotto.achtung.com with esmtp; Fri, 09 Jan 2004 17:47:54 +0800 Message-ID: <3FFE789E.2070805@achtung.com> Date: Fri, 09 Jan 2004 17:47:10 +0800 From: Albert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vinum-devel@auug.org.au Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Vinum-devel] System died Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Hmm.. in mucking with all the vinum stuff.. My root fs got corrupted (Don't know how) so now the entire system is dead. Stuck in an endless kernel panic <-> reboot cycle.. :-( Oh well.. Albert From grog@lemis.com Fri Jan 9 22:48:00 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blackwater.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id B8528978C5 for ; Fri, 9 Jan 2004 22:47:59 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id E134651219; Fri, 9 Jan 2004 22:47:57 +1030 (CST) Date: Fri, 9 Jan 2004 22:47:57 +1030 From: Greg 'groggy' Lehey To: Albert Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Vinum Crash Message-ID: <20040109121757.GM7617@wantadilla.lemis.com> References: <3FFE774A.4050407@achtung.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gGwQG2l7+sHH0Akr" Content-Disposition: inline In-Reply-To: <3FFE774A.4050407@achtung.com> User-Agent: Mutt/1.4.1i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --gGwQG2l7+sHH0Akr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Friday, 9 January 2004 at 17:41:30 +0800, Albert wrote: > Well.. I should buy a lotto ticket today; I managed to crash vinum and > freebsd about 12 times today... > > I had detached one of the plexes and now I can't reattach it! > > Any ideas? Sure. http://www.vinumvm.org/vinum/how-to-debug.html It would be nice if you would read the documentation first. Greg -- See complete headers for address and phone numbers. --gGwQG2l7+sHH0Akr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE//pv1IubykFB6QiMRAp0tAJ9HU7Urd/3QtRohOgcyXu+UkGor2wCfZ8m7 N1kSrbdXsxMPscCypUTxrzs= =vxb7 -----END PGP SIGNATURE----- --gGwQG2l7+sHH0Akr-- From Bob@VanValzah.Com Sat Jan 10 00:12:41 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from Bastion.VanValzah.Com (Bastion.VanValzah.Com [64.81.228.180]) by www.auug.org.au (Postfix) with ESMTP id 2217A97705 for ; Sat, 10 Jan 2004 00:12:40 +1030 (CST) Received: from Relent.VanValzah.Com (Relent.VanValzah.Com [10.168.60.2]) by Bastion.VanValzah.Com (8.12.9p2/8.12.9) with ESMTP id i09Dg5u5061237; Fri, 9 Jan 2004 07:42:05 -0600 (CST) (envelope-from Bob@VanValzah.Com) Received: from [127.0.0.1] (localhost [127.0.0.1]) by Relent.VanValzah.Com (8.12.9p2/8.12.9) with ESMTP id i09Dg4JK032750; Fri, 9 Jan 2004 07:42:04 -0600 (CST) (envelope-from Bob@VanValzah.Com) Subject: Re: [Vinum-devel] Vinum Install on FreeBSD 5.1 From: Bob Van Valzah To: Albert Cc: vinum-devel@auug.org.au In-Reply-To: <3FFE4E35.9040906@achtung.com> References: <3FFE4E35.9040906@achtung.com> Content-Type: text/plain Message-Id: <1073655723.29597.6.camel@Relent.VanValzah.Com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 09 Jan 2004 07:42:04 -0600 Content-Transfer-Encoding: 7bit Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: On Fri, 2004-01-09 at 00:46, Albert wrote: > Documentation is hairy at best, and I've read all that is available on > it about 20 times, and still made mistakes. Hopefully, I'll find some > time this coming week to write documentation based on my own experience > of setting up Vinum. But once setup, it's fairly transparent. Albert, I had similar experiences, came to similar conclusions, and wrote an article giving a technique for simply installing & configuring vinum. See: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/ This all happened over a year ago. Vinum has progressed in adding some support for root filesystems, but I haven't updated the article for that yet. I'm considering updating it and revising it. You might be in a good spot now to give it a read and try out the advice therein. I'd welcome your feedback. Thanks, Bob From vinum@achtung.com Sat Jan 10 02:33:42 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blotto.achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) by www.auug.org.au (Postfix) with ESMTP id 28737976C2 for ; Sat, 10 Jan 2004 02:33:40 +1030 (CST) Received: from achtung.com (61-219-255-82.HINET-IP.hinet.net [61.219.255.82]) (AUTH: LOGIN albert) by blotto.achtung.com with esmtp; Sat, 10 Jan 2004 00:04:38 +0800 Message-ID: <3FFED0EF.1080900@achtung.com> Date: Sat, 10 Jan 2004 00:03:59 +0800 From: Albert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Van Valzah Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Vinum Install on FreeBSD 5.1 References: <3FFE4E35.9040906@achtung.com> <1073655723.29597.6.camel@Relent.VanValzah.Com> In-Reply-To: <1073655723.29597.6.camel@Relent.VanValzah.Com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Bob, I have read your documentation several times.. It makes perfect sense... AFTER I've tried installing it.. I think Vinum and the bootstrapping of it is like driving a car, you can read all you want, but none of it makes sense until you actually try it. Thanks for the documentation though, it helped a lot. Albert Bob Van Valzah wrote: > On Fri, 2004-01-09 at 00:46, Albert wrote: > >>Documentation is hairy at best, and I've read all that is available on >>it about 20 times, and still made mistakes. Hopefully, I'll find some >>time this coming week to write documentation based on my own experience >>of setting up Vinum. But once setup, it's fairly transparent. > > > Albert, I had similar experiences, came to similar conclusions, and > wrote an article giving a technique for simply installing & configuring > vinum. See: > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/ > > This all happened over a year ago. Vinum has progressed in adding some > support for root filesystems, but I haven't updated the article for that > yet. > > I'm considering updating it and revising it. You might be in a good > spot now to give it a read and try out the advice therein. I'd welcome > your feedback. > > Thanks, > > Bob > > From sdebnath@csociety.ecn.purdue.edu Sat Jan 10 18:04:01 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from csociety.ecn.purdue.edu (csociety.ecn.purdue.edu [128.46.156.155]) by www.auug.org.au (Postfix) with ESMTP id 3E8C197773 for ; Sat, 10 Jan 2004 18:04:01 +1030 (CST) Received: by csociety.ecn.purdue.edu (Postfix, from userid 54568) id 38FB471A6D; Sat, 10 Jan 2004 02:34:00 -0500 (EST) Date: Sat, 10 Jan 2004 02:34:00 -0500 From: Shawn Debnath To: vinum-devel@auug.org.au Message-ID: <20040110073400.GB25628@cs.purdue.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Precedence: first-class Priority: normal Organization: Computer Society, Purdue University Subject: [Vinum-devel] Help port vinum to linux Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Hello, I was wondering if you were still looking for developers to help port vinum to the linux environment? I have been programming in C for over 6 years now, and I have used it for writing every day applications to load balancing apps to operating system kernel (personal pet project). Although my experience has mostly been in the university field (this involves working as a software engineer at our local IT Research & Advanced Computing Dept) I feel strongly that once in, I will be able to quickly grab the concepts and be productive with the newly acquired knowledge. My interest in file systems has recently been initiated after talks with folks from Sun's Colorado facility. Data storage facilities is one of the key areas being researched in the operating systems field (along with networking and security) and I would be very grateful if you give me the opportunity to work with this team. Thank you. Shawn Debnath sdebnath@purdue.edu From grog@lemis.com Sat Jan 10 18:16:32 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blackwater.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id 0F97D97A2D for ; Sat, 10 Jan 2004 18:16:31 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 4CC1851214; Sat, 10 Jan 2004 18:16:29 +1030 (CST) Date: Sat, 10 Jan 2004 18:16:29 +1030 From: Greg 'groggy' Lehey To: Shawn Debnath Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Message-ID: <20040110074629.GU7617@wantadilla.lemis.com> References: <20040110073400.GB25628@cs.purdue.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2h2L1EJYm8bdoDNX" Content-Disposition: inline In-Reply-To: <20040110073400.GB25628@cs.purdue.edu> User-Agent: Mutt/1.4.1i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --2h2L1EJYm8bdoDNX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 10 January 2004 at 2:34:00 -0500, Shawn Debnath wrote: > Hello, > > I was wondering if you were still looking for developers to help port > vinum to the linux environment? Definitely! > I have been programming in C for over 6 years now, and I have used > it for writing every day applications to load balancing apps to > operating system kernel (personal pet project). Although my > experience has mostly been in the university field (this involves > working as a software engineer at our local IT Research & Advanced > Computing Dept) I feel strongly that once in, I will be able to > quickly grab the concepts and be productive with the newly acquired > knowledge. > > My interest in file systems has recently been initiated after talks > with folks from Sun's Colorado facility. Data storage facilities is > one of the key areas being researched in the operating systems field > (along with networking and security) and I would be very grateful if > you give me the opportunity to work with this team. You've come at a good time. I've just finished (but not submitted) a paper about Vinum for Linux.conf.au (http://lca2004.linux.org.au/). It finishes with a request for participation from the Linux community. It could now finish with a statement that you're working on it :-) I'll put the paper up on the web site tomorrow morning my time (it's currently evening), and I'll send out a message about it. Take a look and we can discuss the matter. Greg -- See complete headers for address and phone numbers. --2h2L1EJYm8bdoDNX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE//63VIubykFB6QiMRAkJ/AJ42ABYNdkD0KCGNSWjhWmN17lGFYwCfXD2M 4aKUKOWqMu4GckVa2fg8SpQ= =v2l7 -----END PGP SIGNATURE----- --2h2L1EJYm8bdoDNX-- From sdebnath@csociety.ecn.purdue.edu Sat Jan 10 18:24:03 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from csociety.ecn.purdue.edu (csociety.ecn.purdue.edu [128.46.156.155]) by www.auug.org.au (Postfix) with ESMTP id 4E72097A73; Sat, 10 Jan 2004 18:24:03 +1030 (CST) Received: by csociety.ecn.purdue.edu (Postfix, from userid 54568) id 4201471A6D; Sat, 10 Jan 2004 02:54:02 -0500 (EST) Date: Sat, 10 Jan 2004 02:54:02 -0500 From: Shawn Debnath To: Greg 'groggy' Lehey Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Message-ID: <20040110075402.GA26057@cs.purdue.edu> References: <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040110074629.GU7617@wantadilla.lemis.com> User-Agent: Mutt/1.3.28i Precedence: first-class Priority: normal Organization: Computer Society, Purdue University Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: > Definitely! Awesome :) > You've come at a good time. I've just finished (but not submitted) a > paper about Vinum for Linux.conf.au (http://lca2004.linux.org.au/). > It finishes with a request for participation from the Linux > community. It could now finish with a statement that you're working > on it :-) Wow, this is just being lucky :) > I'll put the paper up on the web site tomorrow morning my time (it's > currently evening), and I'll send out a message about it. Take a look > and we can discuss the matter. Which web site the linux.org.au one or the vinum.auug.au one? Also I would appreciate if we can arrange for a time to meet on IRC/AIM/etc so you may answer some questions for me. I am new to the field of file systems, but I am sure it is going to be an enjoyable one since its an very exciting field of study for me. PS. How many developers do you currently have working on this port? Thanks again! Shawn From kopts@astro.psu.edu Sat Jan 10 21:15:44 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from lonestar.astro.psu.edu (lonestar.astro.psu.edu [128.118.147.184]) by www.auug.org.au (Postfix) with ESMTP id 26E509798C; Sat, 10 Jan 2004 21:15:40 +1030 (CST) Received: from vela.astro.psu.edu (vela.astro.psu.edu [128.118.147.228]) by lonestar.astro.psu.edu (Postfix) with ESMTP id 3413D1DBC; Sat, 10 Jan 2004 05:45:32 -0500 (EST) Date: Sat, 10 Jan 2004 05:42:02 -0500 (EST) From: Alexey Koptsevich To: Shawn Debnath Cc: Greg 'groggy' Lehey , Subject: Re: [Vinum-devel] Help port vinum to linux In-Reply-To: <20040110075402.GA26057@cs.purdue.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Hi, > PS. How many developers do you currently have working on this port? Actually, I decided to start to work on this project. But my experience in system programming is very limited, and I am still learning how vinum works on the code level. I would be glad to join the project leaded by somebody else. I would be glad if we coordinate efforts. Thanks, Alex From Robert.VARGA@orange.sk Sun Jan 11 08:48:08 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from avmail.orange.sk (avmail.orange.sk [213.151.208.38]) by www.auug.org.au (Postfix) with SMTP id C2AAD9798B; Sun, 11 Jan 2004 08:48:05 +1030 (CST) Received: from MAIL2.intranet.orange.sk ([10.2.90.13]) by avmail.orange.sk (SAVSMTP 3.1.3.37) with SMTP id M2004011023174720033 ; Sat, 10 Jan 2004 23:17:47 +0100 Subject: RE: [Vinum-devel] Help port vinum to linux Date: Sat, 10 Jan 2004 23:17:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <39AE33280C2D2449AB9C8E035F7D74128189B8@MAIL2.intranet.orange.sk> content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Vinum-devel] Help port vinum to linux Thread-Index: AcPXZvM+iBHZKzVrSUKYVELQVndghQAX04qQ From: "VARGA, Robert" To: "Alexey Koptsevich" , "Shawn Debnath" Cc: "Greg 'groggy' Lehey" , Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: Hi, I considered starting to work on this port, yet I never got around to looking at the sources :-)=20 Anyway, I am not scared of Linux kernel (I had a couple of never-released pet projects), so time to time I can lend you a hand. -- Robert Varga Sun Systems Administrator IS Operation Orange Slovensko You don't have to be crazy to work here, but it helps. -- Captain John J. Sheridan, Babylon 5 -----Original Message----- From: Alexey Koptsevich [mailto:kopts@astro.psu.edu]=20 Sent: Saturday, January 10, 2004 11:42 AM To: Shawn Debnath Cc: Greg 'groggy' Lehey; vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Hi, > PS. How many developers do you currently have working on this port? Actually, I decided to start to work on this project. But my experience in system programming is very limited, and I am still learning how vinum works on the code level. I would be glad to join the project leaded by somebody else. I would be glad if we coordinate efforts. Thanks, Alex _______________________________________________ Vinum-devel mailing list Vinum-devel@auug.org.au http://www.auug.org.au/mailman/listinfo/vinum-devel Hosted by AUUG (http://www.auug.org.au/). =20 Join AUUG at http://www.auug.org.au/info#join. From grog@lemis.com Sun Jan 11 14:18:39 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blackwater.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id 7E18497772 for ; Sun, 11 Jan 2004 14:18:37 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 7830F51211; Sun, 11 Jan 2004 14:18:35 +1030 (CST) Date: Sun, 11 Jan 2004 14:18:35 +1030 From: Greg 'groggy' Lehey To: Shawn Debnath , Alexey Koptsevich , "VARGA, Robert" Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Message-ID: <20040111034835.GH7617@wantadilla.lemis.com> References: <39AE33280C2D2449AB9C8E035F7D74128189B8@MAIL2.intranet.orange.sk> <20040110075402.GA26057@cs.purdue.edu> <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040110080003.GA26127@cs.purdue.edu> <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HLGFn5Z83C1flW5S" Content-Disposition: inline In-Reply-To: <39AE33280C2D2449AB9C8E035F7D74128189B8@MAIL2.intranet.orange.sk> <20040110080003.GA26127@cs.purdue.edu> <20040110075402.GA26057@cs.purdue.edu> User-Agent: Mutt/1.4.1i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --HLGFn5Z83C1flW5S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 10 January 2004 at 2:54:02 -0500, Shawn Debnath wrote: >> You've come at a good time. I've just finished (but not submitted) a >> paper about Vinum for Linux.conf.au (http://lca2004.linux.org.au/). >> It finishes with a request for participation from the Linux >> community. It could now finish with a statement that you're working >> on it :-) > > Wow, this is just being lucky :) Me too. Now I have something to say during the presentation next Friday :-) >> I'll put the paper up on the web site tomorrow morning my time (it's >> currently evening), and I'll send out a message about it. Take a look >> and we can discuss the matter. > > Which web site the linux.org.au one or the vinum.auug.au one? Neither. http://www.vinumvm.org/Testing/paper.pdf. This is a temporary location, and please don't distribute the paper. On the other hand, feedback is more than welcome. > Also I would appreciate if we can arrange for a time to meet on > IRC/AIM/etc so you may answer some questions for me. I am new to the > field of file systems, but I am sure it is going to be an enjoyable > one since its an very exciting field of study for me. I'd honestly prefer to handle this on the mailing list. The mailing list has a number of advantages: - It provides a record of what was said. - It gives people a chance to think before answering :-) - It doesn't require everybody to be online at the same time. Given the shape of the world, this is important. For example, you're 8 1/2 hours away from me, and in a few months it'll be 10 1/2. On Saturday, 10 January 2004 at 3:00:03 -0500, Shawn Debnath wrote: > >> PS. How many developers do you currently have working on this port? > > Err, ignore that :) Are we going to be the only two working on it? Count on me for support and answering questions, but not too much work: I have too much else to do. With any luck, we'll get some more people involved, both on this list and from my paper next week. On Saturday, 10 January 2004 at 5:42:02 -0500, Alexey Koptsevich wrote: > > Hi, > >> PS. How many developers do you currently have working on this port? > > Actually, I decided to start to work on this project. But my experience in > system programming is very limited, and I am still learning how vinum > works on the code level. I would be glad to join the project leaded by > somebody else. I would be glad if we coordinate efforts. I'm not sure that I can do project management, but it's a possibility. On Saturday, 10 January 2004 at 23:17:47 +0100, VARGA, Robert wrote: > Hi, > > I considered starting to work on this port, yet I never got around to > looking at the sources :-) > > Anyway, I am not scared of Linux kernel (I had a couple of > never-released pet projects), so time to time I can lend you a hand. Sounds good. Do we have a volunteer to get the sources up somewhere? Maybe sourceforge? We have a project, but it's pretty dead. I seem to recall a volunteer a while back, but not much came of it, possibly my fault. Greg -- See complete headers for address and phone numbers. --HLGFn5Z83C1flW5S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAAMeTIubykFB6QiMRArfoAJ9BTK0WAkm2HbHG2flXB2lZTkBw9QCgrC0y vEszN3z1u9z2ZCA7uqgtSPI= =aYhm -----END PGP SIGNATURE----- --HLGFn5Z83C1flW5S-- From sdebnath@csociety.ecn.purdue.edu Sun Jan 11 14:51:08 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from csociety.ecn.purdue.edu (csociety.ecn.purdue.edu [128.46.156.155]) by www.auug.org.au (Postfix) with ESMTP id B2F2D976DB for ; Sun, 11 Jan 2004 14:51:07 +1030 (CST) Received: by csociety.ecn.purdue.edu (Postfix, from userid 54568) id 937DD71F64; Sat, 10 Jan 2004 23:21:05 -0500 (EST) Date: Sat, 10 Jan 2004 23:21:05 -0500 From: Shawn Debnath To: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Message-ID: <20040111042105.GA14850@cs.purdue.edu> References: <20040110075402.GA26057@cs.purdue.edu> <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040110080003.GA26127@cs.purdue.edu> <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040111034835.GH7617@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111034835.GH7617@wantadilla.lemis.com> User-Agent: Mutt/1.3.28i Precedence: first-class Priority: normal Organization: Computer Society, Purdue University Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: > I'd honestly prefer to handle this on the mailing list. The mailing > list has a number of advantages: > > - It provides a record of what was said. > - It gives people a chance to think before answering :-) > - It doesn't require everybody to be online at the same time. Given > the shape of the world, this is important. For example, you're 8 > 1/2 hours away from me, and in a few months it'll be 10 1/2. > Sounds good. Do we have a volunteer to get the sources up somewhere? > Maybe sourceforge? We have a project, but it's pretty dead. I seem > to recall a volunteer a while back, but not much came of it, possibly > my fault. We can certainly use the sourceforge to host the cvs. My question is if we are going to use SF, should we use the lists provided by SF? They archive all the messages via Geocrawler, in case of personal email disasters. Did a little research, project name is vinum on SF. Greg, you seem to be the sole member of it. If you decide using SF is a good idea, please add 'sdebnath' to the group :) I can take care of administration tasks on SF, if you want. Alexey seems to be the right person to make incharge of putting the sources in the cvs. Alexey are you up for it? Rob, and Alexey, t would be a good idea to email your sourceforge username so you can be added to the group. > Count on me for support and answering questions, but not too much > work: I have too much else to do. With any luck, we'll get some more > people involved, both on this list and from my paper next week. Rob, and Alexey are interested in working on this. > I'm not sure that I can do project management, but it's a possibility. I certainly do not have enough knowledge about Vinum to handle project management responsibility. So its still up for grabs. Shawn From grog@lemis.com Sun Jan 11 15:27:13 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from blackwater.lemis.com (unknown [192.109.197.80]) by www.auug.org.au (Postfix) with ESMTP id 522B197804 for ; Sun, 11 Jan 2004 15:27:11 +1030 (CST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 7849751211; Sun, 11 Jan 2004 15:27:09 +1030 (CST) Date: Sun, 11 Jan 2004 15:27:09 +1030 From: Greg 'groggy' Lehey To: Shawn Debnath Cc: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Message-ID: <20040111045709.GI7617@wantadilla.lemis.com> References: <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040110080003.GA26127@cs.purdue.edu> <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040111034835.GH7617@wantadilla.lemis.com> <20040111042105.GA14850@cs.purdue.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="79yJmXxfh+IGDHgZ" Content-Disposition: inline In-Reply-To: <20040111042105.GA14850@cs.purdue.edu> User-Agent: Mutt/1.4.1i Organization: AUUG: Australian UNIX and Open Systems User Group Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.auug.org.au/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: --79yJmXxfh+IGDHgZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Saturday, 10 January 2004 at 23:21:05 -0500, Shawn Debnath wrote: >> I'd honestly prefer to handle this on the mailing list. The mailing >> list has a number of advantages: >> >> - It provides a record of what was said. >> - It gives people a chance to think before answering :-) >> - It doesn't require everybody to be online at the same time. Given >> the shape of the world, this is important. For example, you're 8 >> 1/2 hours away from me, and in a few months it'll be 10 1/2. > >> Sounds good. Do we have a volunteer to get the sources up somewhere? >> Maybe sourceforge? We have a project, but it's pretty dead. I seem >> to recall a volunteer a while back, but not much came of it, possibly >> my fault. > > We can certainly use the sourceforge to host the cvs. My question is if > we are going to use SF, should we use the lists provided by SF? They > archive all the messages via Geocrawler, in case of personal email > disasters. This could be a good idea. I set up the Sourccforge project some time ago when I had a little bit of time over, but it ran out before I got things running properly. > Did a little research, project name is vinum on SF. Greg, you seem > to be the sole member of it. If you decide using SF is a good idea, > please add 'sdebnath' to the group :) I can take care of > administration tasks on SF, if you want. Done. I've given you all privileges. > Alexey seems to be the right person to make incharge of putting the > sources in the cvs. Alexey are you up for it? Rob, and Alexey, t > would be a good idea to email your sourceforge username so you can > be added to the group. Can you add them if they're interested? >> I'm not sure that I can do project management, but it's a possibility. > > I certainly do not have enough knowledge about Vinum to handle project > management responsibility. So its still up for grabs. I'd prefer somebody else to do it. It would be nice for them to have had some experience, of course :-) I'm wondering what to do with the source code. Currently I keep a "super source" with lots of #ifdefs, and I pass it through a Makefile to create the versions for the individual OS platforms. The idea is to have automatic propagation of platform-independent changes, but it's a bit hairy. I think at present it would be worthwhile creating a "base" Linux version. It won't even come close to compiling, because it's a WWP (Work Without Progress), but it might be a starting point.=20 Greg -- See complete headers for address and phone numbers. --79yJmXxfh+IGDHgZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAANelIubykFB6QiMRAgH6AKCO/wGZ7DkUciyMiD9eRSLPZ+rH+QCfUrkU vPnvRiEwuUOYSxdk7kCCER8= =B99B -----END PGP SIGNATURE----- --79yJmXxfh+IGDHgZ-- From sdebnath@csociety.ecn.purdue.edu Sun Jan 11 15:52:05 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from csociety.ecn.purdue.edu (csociety.ecn.purdue.edu [128.46.156.155]) by www.auug.org.au (Postfix) with ESMTP id 4A62B97700 for ; Sun, 11 Jan 2004 15:52:05 +1030 (CST) Received: by csociety.ecn.purdue.edu (Postfix, from userid 54568) id 4D33071C05; Sun, 11 Jan 2004 00:22:04 -0500 (EST) Date: Sun, 11 Jan 2004 00:22:04 -0500 From: Shawn Debnath To: vinum-devel@auug.org.au Subject: Re: [Vinum-devel] Help port vinum to linux Message-ID: <20040111052204.GA16248@cs.purdue.edu> References: <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040110080003.GA26127@cs.purdue.edu> <20040110073400.GB25628@cs.purdue.edu> <20040110074629.GU7617@wantadilla.lemis.com> <20040110075402.GA26057@cs.purdue.edu> <20040111034835.GH7617@wantadilla.lemis.com> <20040111042105.GA14850@cs.purdue.edu> <20040111045709.GI7617@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111045709.GI7617@wantadilla.lemis.com> User-Agent: Mutt/1.3.28i Precedence: first-class Priority: normal Organization: Computer Society, Purdue University Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: > > We can certainly use the sourceforge to host the cvs. My question is if > > we are going to use SF, should we use the lists provided by SF? They > > archive all the messages via Geocrawler, in case of personal email > > disasters. > > This could be a good idea. I set up the Sourccforge project some time > ago when I had a little bit of time over, but it ran out before I got > things running properly. Okay, I added a vinum-devel mailing list. If you approve, we can start using it once its activated. I have added vargarob to the group as a developer, and will add alexey once he sends his username in. Would they need admin privileges? They have full access to all the different parts of SF. > I'm wondering what to do with the source code. Currently I keep a > "super source" with lots of #ifdefs, and I pass it through a Makefile > to create the versions for the individual OS platforms. The idea is > to have automatic propagation of platform-independent changes, but > it's a bit hairy. > > I think at present it would be worthwhile creating a "base" Linux > version. It won't even come close to compiling, because it's a WWP > (Work Without Progress), but it might be a starting point. Starting off with a base definitely sounds like a good idea. This would give us time to learn and familiarize ourselves with the code (if we haven't done so already) and get it to a compiling state. I am guessing this wouldn't be architecture dependent at all. So would the next move be checking in a clean (base linux) version of the "super source" into the SF cvs? Shawn From Robert.VARGA@orange.sk Mon Jan 12 05:59:35 2004 Return-Path: X-Original-To: vinum-devel@auug.org.au Delivered-To: vinum-devel@auug.org.au Received: from avmail.orange.sk (avmail.orange.sk [213.151.208.38]) by www.auug.org.au (Postfix) with SMTP id E7CDD97AB5; Mon, 12 Jan 2004 05:59:33 +1030 (CST) Received: from MAIL2.intranet.orange.sk ([10.2.90.13]) by avmail.orange.sk (SAVSMTP 3.1.3.37) with SMTP id M2004011120293125687 ; Sun, 11 Jan 2004 20:29:31 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Vinum-devel] Help port vinum to linux X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Sun, 11 Jan 2004 20:29:32 +0100 Message-ID: <39AE33280C2D2449AB9C8E035F7D7412818A18@MAIL2.intranet.orange.sk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Vinum-devel] Help port vinum to linux Thread-Index: AcPX9dJ4GpgS+UsCQtCqO1WNcYjggwAgOTYw From: "VARGA, Robert" To: "Greg 'groggy' Lehey" Cc: Sender: vinum-devel-admin@auug.org.au Errors-To: vinum-devel-admin@auug.org.au X-BeenThere: vinum-devel@auug.org.au X-Mailman-Version: 2.0.13 Precedence: bulk List-Unsubscribe: , List-Id: A mailing list for people developing the Vinum Volume Manager List-Post: List-Help: List-Subscribe: , List-Archive: > -----Original Message----- > From: Greg 'groggy' Lehey [mailto:Greg.Lehey@auug.org.au]=20 > Sent: Sunday, January 11, 2004 4:49 AM > To: Shawn Debnath; Alexey Koptsevich; VARGA, Robert > Cc: vinum-devel@auug.org.au > Subject: Re: [Vinum-devel] Help port vinum to linux >=20 > On Saturday, 10 January 2004 at 2:54:02 -0500, Shawn Debnath wrote: > >> You've come at a good time. I've just finished (but not=20 > submitted) a > >> paper about Vinum for Linux.conf.au (http://lca2004.linux.org.au/). > >> It finishes with a request for participation from the Linux > >> community. It could now finish with a statement that=20 > you're working > >> on it :-) > > > > Wow, this is just being lucky :) >=20 > Me too. Now I have something to say during the presentation next > Friday :-) >=20 > >> I'll put the paper up on the web site tomorrow morning my=20 > time (it's > >> currently evening), and I'll send out a message about it. =20 > Take a look > >> and we can discuss the matter. > > > > Which web site the linux.org.au one or the vinum.auug.au one? >=20 > Neither. http://www.vinumvm.org/Testing/paper.pdf. This is a > temporary location, and please don't distribute the paper. On the > other hand, feedback is more than welcome. I just skimmed through the paper. Couple of notes regarding Linux architecture: 1. As for the plex/disk/subdisk limits, in 2.6.x (which is what we'll want to start with) dev_t is 32 bit, but I don't remember the exact major:minor split. For 2.7.x, completely dynamic device numbers are being considered. 2. With regard to memory allocation issues, these could probably be resolved using pre-allocated emergency memory pool. 3. Linux does support kernel threads, which will help in RAID5 according to the paper (i.e. we'd create an 'IO completion thread' to handle the second set of IO requests) 4. And finally: yes, I'd prefer vinum to anything freely available on Linux today :-) > On Saturday, 10 January 2004 at 3:00:03 -0500, Shawn Debnath wrote: > > > >> PS. How many developers do you currently have working on this port? > > > > Err, ignore that :) Are we going to be the only two working on it? >=20 > Count on me for support and answering questions, but not too much > work: I have too much else to do. With any luck, we'll get some more > people involved, both on this list and from my p