From owner-freebsd-geom@FreeBSD.ORG Tue Jul 6 11:32:44 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47F4816A4CE for ; Tue, 6 Jul 2004 11:32:44 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC3C843D2D for ; Tue, 6 Jul 2004 11:32:43 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id BFBD6ACAEE; Tue, 6 Jul 2004 13:32:42 +0200 (CEST) Date: Tue, 6 Jul 2004 13:32:42 +0200 From: Pawel Jakub Dawidek To: geom@freebsd.org Message-ID: <20040706113242.GK12007@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T0VxxuQkR4DcuMht" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 Subject: GEOM and retaste. X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2004 11:32:44 -0000 --T0VxxuQkR4DcuMht Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I'm still fighting with 'stop' command for geom_mirror class. It should works, just like in my other class: turn off the given geom/provider/device. But for geom_mirror, I need to open all disks with r1w1e1 perms, so when I call 'stop' command and I close those disks, they are retasted and mirror is created once again. I don't want to touch metadata to mark all disks as inactve, because after kld module is unloaded and loaded again I want this mirror to be setup automatically. Any ideas? I don't want to introduce any hacks to do it, for example I can create a list of disks which I'm planing to close and on retaste ignore them and remove from the list (but probably there could be a race, because retaste event may be canceled, so there will be a memory leak). I proposed to not send retaste event to class which made the last close for provider, but phk disagree with it. So maybe we can do something in the middle? We can pass a flag for retaste which will tell me, that I was the one who made the last close? --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --T0VxxuQkR4DcuMht Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA6o3aForvXbEpPzQRAnB8AKCcljc7eIUuFNb5c1QC07yWbhZc1wCdE7hu uN5idtMHSodH8D4Q+0onWX0= =YLTJ -----END PGP SIGNATURE----- --T0VxxuQkR4DcuMht--