From owner-freebsd-geom@FreeBSD.ORG Sun May 27 14:35:09 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6544F16A475 for ; Sun, 27 May 2007 14:35:09 +0000 (UTC) (envelope-from afields@ncf.ca) Received: from saruman.ncf.ca (saruman.ncf.ca [134.117.136.37]) by mx1.freebsd.org (Postfix) with ESMTP id 3A67113C48A for ; Sun, 27 May 2007 14:35:09 +0000 (UTC) (envelope-from afields@ncf.ca) Received: from ncf.ca (mail [134.117.136.45]) by saruman.ncf.ca (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JIP00LLSCEKAF@saruman.ncf.ca> for freebsd-geom@freebsd.org; Sun, 27 May 2007 09:35:08 -0400 (EDT) Received: from [74.104.133.87] by saruman.ncf.ca (mshttpd); Sun, 27 May 2007 09:35:08 -0400 Date: Sun, 27 May 2007 09:35:08 -0400 From: Allan Fields To: freebsd-geom@freebsd.org Message-id: <38bbc5392a4a.392a4a38bbc5@ncf.ca> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 Patch 2 (built Jul 14 2004) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal Subject: slice entries + stripe/mirror X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2007 14:35:09 -0000 Last night I ran into a few issues. Slice entries such as both /dev/ad12bs1 and /dev/ad12cs1 when I've created a FreeBSD slice/partition on provider /dev/ad12 and previously had /dev/ad12s1[bcd] proper seem error prone. As a work around I've simply updated /etc/fstab to use /dev/ad{8,10,12,14}b as swap. E.g. gstripe is using consumers /dev/ad{8,10}d which previously were showing up as /dev/ad{8,10}s1d. The change occurred when I did geom_{stripe,mirror}_load="YES" in loader.conf. I've seen this behaviour for a while now since early 5.x and am still seeing it in 6.2-RELEASE. It drives the rc scripts bonkers because they can't find the correct device entries anymore, so files like /etc/fstab and /etc/rc.conf have to be updated. Anytime device entries like /dev/ad0bs1 start to appear, as a sysadmin/user you might question why. ("Can't FreeBSD get it the right way around?", etc.) The other issue is related to mirrors and setting geom_mirror_load="YES" in /boot/loader.conf. I had a dormant or erroneous mirror entry gm0 on provider ad0 which is my boot disk. (Did I even put that there?) While this wasn't an issue when I was configurting mirrors manually, I started the system up to find a new gm0 mirror that I had obviously forgotten about now existed, and worse, it auto-activated it in addition to the other mirror devices removing the dev entries for ad0s1[a-g] but thankfully keeping the disklabel and creating mirror/gm0s1[a-g]. Just a thought.. The question with on-disk meta-data/auto that can possibly do funky things to disks if they are plugged in on the wrong channel, etc. is a concern. Are there cases where it is possible for an admin to inadvertently screw their geom config and/or destroy volumes? Maybe the user should be (default, optional) prompted first before a stripe or raid starts to rebuild at boot time? Prompt user first: I do know is possible with eli password prompt at boot for instance. As long as it "just works", there isn't any issue, but what border-line cases exist, I'd like to know. Thanks.. Allan Fields From owner-freebsd-geom@FreeBSD.ORG Mon May 28 11:08:23 2007 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 840E716A4D1 for ; Mon, 28 May 2007 11:08:23 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 73D1A13C44B for ; Mon, 28 May 2007 11:08:23 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4SB8NcM068460 for ; Mon, 28 May 2007 11:08:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4SB8Mxb068456 for freebsd-geom@FreeBSD.org; Mon, 28 May 2007 11:08:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 May 2007 11:08:22 GMT Message-Id: <200705281108.l4SB8Mxb068456@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 11:08:23 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/73177 geom kldload geom_* causes panic due to memory exhaustion o kern/76538 geom [gbde] nfs-write on gbde partition stalls and continue o kern/83464 geom [geom] [patch] Unhandled malloc failures within libgeo o kern/84556 geom [geom] GBDE-encrypted swap causes panic at shutdown o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o kern/89102 geom [geom_vfs] [panic] panic when forced unmount FS from u o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/90582 geom [geom_mirror] [panic] Restore cause panic string (ffs_ o kern/98034 geom [geom] dereference of NULL pointer in acd_geom_detach o kern/104389 geom [geom] [patch] sys/geom/geom_dump.c doesn't encode XML 10 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/78131 geom gbde "destroy" not working. o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/94632 geom [geom] Kernel output resets input while GELI asks for f kern/105390 geom [geli] filesystem on a md backed by sparse file with s o kern/107707 geom [geom] [patch] add new class geom_xbox360 to slice up p bin/110705 geom gmirror control utility does not exit with correct exi 6 problems total. From owner-freebsd-geom@FreeBSD.ORG Tue May 29 14:22:48 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B02C16A400 for ; Tue, 29 May 2007 14:22:48 +0000 (UTC) (envelope-from gianrubio@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id F37B213C45A for ; Tue, 29 May 2007 14:22:45 +0000 (UTC) (envelope-from gianrubio@gmail.com) Received: by an-out-0708.google.com with SMTP id d23so543247and for ; Tue, 29 May 2007 07:22:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=lMXVubojM6NqbvTx57XnLV8ZpBTjEpXDk6ElFy69jDmPmqx4mapuUjO71BP8GFHutOcDVaJCzQtqxXoqngZKdUiNOOxCTvLnqKrciNVrJFZZITfGepSh5Xd7IWh7ra9IgxzfmGxwAD3F/VLGtSntjeeU/WbrA/udQXuMr+xpaIg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=CMFurzHxR/FcIKf62KNpjWdm1wAQXwkpfJf0OafrdjL6KbxlWszJftaHXcPkjvY9Pnv7NUQsxPb0vWAzWhmlRjp/7qjYvLnfDa1cq/YT3MBS0xUDfU01jYaoCGiBUx/IxA77wzALEnIVoShcRoWZRxHcq2OMJ+kX4AiedT/NZio= Received: by 10.142.110.3 with SMTP id i3mr214072wfc.1180446962835; Tue, 29 May 2007 06:56:02 -0700 (PDT) Received: by 10.143.16.12 with HTTP; Tue, 29 May 2007 06:56:02 -0700 (PDT) Message-ID: Date: Tue, 29 May 2007 10:56:02 -0300 From: "Giancarlo Rubio" To: freebsd-geom@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with gstripe X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 14:22:48 -0000 Hi all: I'm using gstripe to create a raid 0, freebsd 6.2, and have a problem. My disk's ad1: DMA limited to UDMA33, controller found non-ATA66 cable ad1: 190782MB at ata0-slave UDMA33 ad4: 381554MB at ata2-master SATA150 ad6: 381553MB at ata3-master SATA150 My strip gstripe list gs Geom name: gs State: UP Status: Total=3, Online=3 Type: MANUAL Stripesize: 4096 ID: 1880939807 Providers: 1. Name: stripe/gs Mediasize: 600148942848 (559G) Sectorsize: 512 Mode: r1w1e1 Consumers: 1. Name: ad1 Mediasize: 200049647616 (186G) Sectorsize: 512 Mode: r1w1e2 Number: 0 2. Name: ad6 Mediasize: 400087375360 (373G) Sectorsize: 512 Mode: r1w1e2 Number: 1 3. Name: ad4s1g Mediasize: 392643118080 (366G) Sectorsize: 512 Mode: r1w1e2 Number: 2 If you look the strip show 559G. 559G is only ad1 and ad6 not ad4s1g. this disk are up an functional on strip gstripe status -s stripe/gs UP ad1 stripe/gs UP ad6 stripe/gs UP ad4s1g Are a problem on gstripe or a mismatch in my concepts? -- Giancarlo Rubio "Linux is for people who hate Windows, BSD is for people who love UNIX" Freebsd-BR User #88 From owner-freebsd-geom@FreeBSD.ORG Tue May 29 14:29:07 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EEAF716A400 for ; Tue, 29 May 2007 14:29:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 8709813C43E for ; Tue, 29 May 2007 14:29:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 6041145696; Tue, 29 May 2007 16:29:05 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 030C045684; Tue, 29 May 2007 16:28:58 +0200 (CEST) Date: Tue, 29 May 2007 16:28:39 +0200 From: Pawel Jakub Dawidek To: Giancarlo Rubio Message-ID: <20070529142839.GA50663@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: Problem with gstripe X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 14:29:08 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 29, 2007 at 10:56:02AM -0300, Giancarlo Rubio wrote: > Hi all: >=20 > I'm using gstripe to create a raid 0, freebsd 6.2, and have a problem. >=20 > My disk's > ad1: DMA limited to UDMA33, controller found non-ATA66 cable > ad1: 190782MB at ata0-slave UDMA33 > ad4: 381554MB at ata2-master SATA150 > ad6: 381553MB at ata3-master SATA150 >=20 > My strip >=20 > gstripe list gs > Geom name: gs > State: UP > Status: Total=3D3, Online=3D3 > Type: MANUAL > Stripesize: 4096 > ID: 1880939807 > Providers: > 1. Name: stripe/gs > Mediasize: 600148942848 (559G) > Sectorsize: 512 > Mode: r1w1e1 > Consumers: > 1. Name: ad1 > Mediasize: 200049647616 (186G) > Sectorsize: 512 > Mode: r1w1e2 > Number: 0 > 2. Name: ad6 > Mediasize: 400087375360 (373G) > Sectorsize: 512 > Mode: r1w1e2 > Number: 1 > 3. Name: ad4s1g > Mediasize: 392643118080 (366G) > Sectorsize: 512 > Mode: r1w1e2 > Number: 2 >=20 > If you look the strip show 559G. 559G is only ad1 and ad6 not ad4s1g. Interesting coincidence... It's actually 3 * , ie. 3*186GB. If you want to use entire space, then use gconcat(8). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGXDiWForvXbEpPzQRApDTAKC8uhB6Iiuhd/f68grQLDMSfP89IgCfTHmM t0bo+6wg4mXzYlDb/pRLfNw= =8HZq -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- From owner-freebsd-geom@FreeBSD.ORG Fri Jun 1 00:36:50 2007 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5547E16A400; Fri, 1 Jun 2007 00:36:50 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 087EA13C465; Fri, 1 Jun 2007 00:36:50 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by postfix1-g20.free.fr (Postfix) with ESMTP id 4E35610F97FD; Fri, 1 Jun 2007 00:44:31 +0200 (CEST) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 0D46044405; Fri, 1 Jun 2007 00:44:30 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 552079C442; Thu, 31 May 2007 22:44:27 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 260A6405B; Fri, 1 Jun 2007 00:44:27 +0200 (CEST) Date: Fri, 1 Jun 2007 00:44:27 +0200 From: Jeremie Le Hen To: pjd@FreeBSD.org Message-ID: <20070531224427.GU31507@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-geom@FreeBSD.org Subject: Difference between setting geli(8) key when attached or detached X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2007 00:36:50 -0000 Hi Pawel, I dare to contact you because I'm studying GELI's code and I found a piece of code I'm not sure to understand, although I've read phk's GEOM tutorial thoroughly. >From what I've undertood (please, correct me if I'm wrong), a "spoiled" event is ``posted when a provider gets a non-zero access count. All attached providers, except the guilty party, are notified.'' geli(8)'s "setkey" command uses two different code paths, depending on whether the provider is attached or not. If is it attached, it seems to use the GEOM kernel part to update the key while if it is detached it writes it directly from userland. My thought is that the provider being modified is not notified by the GEOM framework. Am I right? Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-geom@FreeBSD.ORG Fri Jun 1 04:26:41 2007 Return-Path: X-Original-To: freebsd-geom@FreeBSD.org Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27E9016A421 for ; Fri, 1 Jun 2007 04:26:41 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id BB73F13C48C for ; Fri, 1 Jun 2007 04:26:39 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1E181456AB; Fri, 1 Jun 2007 06:26:38 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 000E745681; Fri, 1 Jun 2007 06:26:29 +0200 (CEST) Date: Fri, 1 Jun 2007 06:26:14 +0200 From: Pawel Jakub Dawidek To: Jeremie Le Hen Message-ID: <20070601042614.GB1223@garage.freebsd.pl> References: <20070531224427.GU31507@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DBIVS5p969aUjpLe" Content-Disposition: inline In-Reply-To: <20070531224427.GU31507@obiwan.tataz.chchile.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-geom@FreeBSD.org Subject: Re: Difference between setting geli(8) key when attached or detached X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2007 04:26:41 -0000 --DBIVS5p969aUjpLe Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 01, 2007 at 12:44:27AM +0200, Jeremie Le Hen wrote: > Hi Pawel, >=20 > I dare to contact you because I'm studying GELI's code and I found > a piece of code I'm not sure to understand, although I've read phk's > GEOM tutorial thoroughly. >=20 > >From what I've undertood (please, correct me if I'm wrong), a > "spoiled" event is ``posted when a provider gets a non-zero access > count. All attached providers, except the guilty party, are > notified.'' s/non-zero access count/non-zero write access count/ Here is the thing. When your class makes decisions based on provider's on-disk metadata, you want to receive spoil event and self-destruct, because open for write means that someone may modify your metadata. Then, on last write close, taste event is send and your class can read eventually modified metadata once again. > geli(8)'s "setkey" command uses two different code paths, depending > on whether the provider is attached or not. If is it attached, > it seems to use the GEOM kernel part to update the key while > if it is detached it writes it directly from userland. >=20 > My thought is that the provider being modified is not notified > by the GEOM framework. Am I right? GELI doesn't do autoconfiguration. The only place when GELI uses taste event is before root file system is mounted, so it can ask for a passphrase when needed. Not sure if this answers your question... --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --DBIVS5p969aUjpLe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGX5/mForvXbEpPzQRAjYgAKDqgxKaYPEekLIHsFR818K/jfUhYACgg9LM 0eJB9oQZoROXD3GeaW4T2GI= =yiLg -----END PGP SIGNATURE----- --DBIVS5p969aUjpLe--