From owner-freebsd-stable@FreeBSD.ORG Sun Dec 19 09:50:55 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93CA816A4CE for ; Sun, 19 Dec 2004 09:50:55 +0000 (GMT) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EA3043D2D for ; Sun, 19 Dec 2004 09:50:55 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-227.de.inter.net ([213.73.76.227] helo=current.best-eng.de) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 1CfxiH-0003Df-00; Sun, 19 Dec 2004 10:50:53 +0100 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iBJ9oqK9001176; Sun, 19 Dec 2004 10:50:52 +0100 (CET) (envelope-from msch@snafu.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id iBJ9oqT2001175; Sun, 19 Dec 2004 10:50:52 +0100 (CET) (envelope-from msch@snafu.de) X-Authentication-Warning: current.best-eng.de: matthias set sender to msch@snafu.de using -f From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-stable@freebsd.org Date: Sun, 19 Dec 2004 10:50:52 +0100 User-Agent: KMail/1.7.1 References: <41C48A6F.7000203@barnabas.dk> <1103416078.6339.4.camel@zappa.Chelsea-Ct.Org> <20041219061221.GA977@sauron.barnabas.dk> In-Reply-To: <20041219061221.GA977@sauron.barnabas.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412191050.52445.msch@snafu.de> cc: Nikolaj Hansen Subject: Re: FreeBSD 5.3 and vinum upgrade #2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 09:50:55 -0000 Am Sonntag, 19. Dezember 2004 07:12 schrieb Nikolaj Hansen: > I gave the 5.3 upgrade another swing. Now the situation is: > > $ uname -a > FreeBSD sauron.barnabas.dk 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat > Dec 18 18:39:09 CET 2004 > root@sauron.barnabas.dk:/usr/obj/usr/src/sys/KERNEL_5_3 i386 Perhaps you better upgrade to RELENG_5 (5.3-STABLE). I'm not aware of any reasons against that in the moment and, besides others, gvinum was improoved since 5.3-RELEASE. But that's your decision... > I think I am understanding a little more of this now. In order to use > my scsi / ATA setup, I need to use the geom_vinum.ko *and* the > vinum.ko modules? Oh no! Don't do that! If you switch to the new geom_vinum, all you *should* need is: geom_vinum_load="YES" in /boot/loader.conf Please comment out (or remove) the vinum*-lines in loader.conf! Additionally you have to change all the entries in /etc/fstab to /dev/gvinum/ / .... (Note the *g*vinum in the device path) But for the first test, you better comment out these lines and try to mount the volumes manually... > [...] > Is this correct? I suppose the ATA drives should be mounted on the > new /dev/gvinum/* and the scsi drives on the /dev/vinum/*? No! As stated above, *all* should now be handled by geom_vinum. > [...] > As I wrote earlier the above loader.conf is not working. If I leave > out the load of the old vinum driver it does not seem to be possible > to mount the scsi drives. If I leave out the geom_vinum a mount of a > drive causes a kernel panic. You *can* use the old "classic" vinum, but it only works if you start classic-vinum *after* the system has come up. You cannot start classic-vinum at boottime with loader.conf, at least it doesn't work for me ('dangling vnode'-panic...). Before you switch to geom_vinum, you should check your partitions as already mentioned in an earlier mail... Try a 'bsdlabel /dev/da1s1' and see, if your vinum-partition does *not* start at an offset of 0. On my disk, it looks as follows: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 4226709 16 vinum c: 4226725 0 unused 0 0 # "raw" part... So here the vinum partition starts at an offset of 16 and therefor is 16 blocks smaller than the whole disk ('c'-partition). That's ok. If it *would* read like that: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 4226725 0 vinum c: 4226725 0 unused 0 0 # "raw" part... it would not work with geom_vinum! The background is, that with geom_vinum you don't need any vinum-partitions any more, further it is possible to use the whole disk (or slice) *without* any BSD partitions. But in the latter case above (with 0-offset), geom_vinum can't distinguish between the whole slice and the 'a'-partition. This did lead to an error (I did not try this with a recent geom_vinum). Anyway, you better spend these 16 blocks offset to be sure IMHO ... > It would be nice if any of you would comment on the above config. I hope it's a bit more clear now... > Perhaps I am ignorant, but it seems to me it would have been easier > to make the regular vinum diver handle geom drives in place of making > a new kernel object? Or perhaps theres a technical reason for not > doing so? Exactly that's the case. If you have to use a completly different infrastructure below, it's obviously more easy to start from scratch... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F