Date: Thu, 21 Apr 2011 09:07:42 +0100 From: Bruce Cran <bruce@cran.org.uk> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: Switch from legacy ata(4) to CAM-based ATA Message-ID: <20110421090742.00005cc0@unknown> In-Reply-To: <DACA5DEF-C004-4818-B658-21045582E480@lists.zabbadoz.net> References: <4DAEAE1B.70207@FreeBSD.org> <20110420203754.GM85668@acme.spoerlein.net> <4DAF46F8.9040004@FreeBSD.org> <BCE89DC7-116D-48E1-BD86-DF986062B0CC@samsco.org> <DACA5DEF-C004-4818-B658-21045582E480@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Apr 2011 07:51:56 +0000 "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> wrote: > a) we MUST HAVE a transition scheme if we cam-base ATA by default. > Something that converts things automatically to whatever? That's not > been done in more than one year. It's not acceptable to update, > reboot and not find the root file system no matter what. We all > agreed on that back then. I do not really care how it's done. I have > been testing cam based ata for a while now on the machines I can cope > with as a developer and even then I screwed the transition partly two > times in the last months. How's a normal user to do that flawlessly? In particular it's fairly common that the mapping isn't adX -> adaX. I've come across cases where ata(4) created ad10, ad12, ad16, etc. which got mapped to ada0, ada1, ada2 etc. When combined with a USB keyboard that often doesn't work at the root mount prompt, recovery can be a bit tricky. -- Bruce Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110421090742.00005cc0>