Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Apr 2011 17:11:02 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Alexander Motin <mav@freebsd.org>
Cc:        "Bjoern A. Zeeb" <bz@freebsd.org>, "Andrey V. Elsukov" <bu7cher@yandex.ru>, Robert Watson <rwatson@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org>
Subject:   Re: Old ATA disk names emulation [Was: Switch from legacy ata(4) to CAM-based ATA]
Message-ID:  <20110425141102.GJ48734@deviant.kiev.zoral.com.ua>
In-Reply-To: <4DB5685A.8010803@FreeBSD.org>
References:  <4DB54BA9.5050901@FreeBSD.org> <4DB55E86.7000805@yandex.ru> <4DB5685A.8010803@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110425141102.GJ48734>