From owner-freebsd-current@FreeBSD.ORG Mon Apr 25 14:11:07 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8877106566B; Mon, 25 Apr 2011 14:11:07 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 57CE88FC0C; Mon, 25 Apr 2011 14:11:06 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p3PEB26o040389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Apr 2011 17:11:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3PEB2DZ059196; Mon, 25 Apr 2011 17:11:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3PEB2Us059132; Mon, 25 Apr 2011 17:11:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 25 Apr 2011 17:11:02 +0300 From: Kostik Belousov To: Alexander Motin Message-ID: <20110425141102.GJ48734@deviant.kiev.zoral.com.ua> References: <4DB54BA9.5050901@FreeBSD.org> <4DB55E86.7000805@yandex.ru> <4DB5685A.8010803@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BbvjD0mU+7XPw0yH" Content-Disposition: inline In-Reply-To: <4DB5685A.8010803@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: "Bjoern A. Zeeb" , "Andrey V. Elsukov" , Robert Watson , FreeBSD-Current Subject: Re: Old ATA disk names emulation [Was: Switch from legacy ata(4) to CAM-based ATA] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 14:11:07 -0000 --BbvjD0mU+7XPw0yH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 25, 2011 at 03:26:02PM +0300, Alexander Motin wrote: > Andrey V. Elsukov wrote: > > On 25.04.2011 14:23, Alexander Motin wrote: > >> What will not work: > >> - old device names won't be seen inside GEOM, so users who hardcoded > >> provider names in gmirror/gstripe/... metadata (not the default > >> behavior) are still in trouble. > >> - patch mimics ATA_STATIC_ID behavior, if user had custom kernel > >> without it, he should update device names manually. > >> - it won't work for users with hot-unplugging ATA controllers (not > >> devices), but I believe it is really rare case. > >> - low-level tools, such as smartmontools, won't be able to work with > >> alias devices, as background ada driver doesn't implements legacy > >> ioctls. May be I could partially fix this. > >> > >> Except those, I think this patch should work for the most of users. > >> > >> Any more objections/ideas? Is this an acceptable solution? > >=20 > > what about new GEOM class? You can create new class instance after > > disk_alloc(), attach it to the new disk and create provider with old-st= yle > > name. It seems this class will be very simple. >=20 > It sounds like less dirty option. I'll try it. Thank you. Won't > re-providing exactly the same device into GEOM create some problems? > glabel and co will connect to each of them (original and legacy) and > report two equal sets of labels. Can you limit the real functionality of this new class to the calls to make_dev_alias(9) ? Ideally, I would think about some extension of the core GEOM, which would take some parameter, lets call it alias name, and will acompany the existing make_dev() calls with parallel make_dev_alias(). --BbvjD0mU+7XPw0yH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk21gPYACgkQC3+MBN1Mb4jyTwCghkGhAwheCpNcp+n2J6n0CTV6 jIsAnj+t7ucjim1G2WKmLB6W3yxGOqwC =6cVV -----END PGP SIGNATURE----- --BbvjD0mU+7XPw0yH--