Date: Tue, 25 Oct 2011 17:01:31 +0200 From: Jason Edwards <sub.mesa@gmail.com> To: freebsd-current@freebsd.org Subject: Re: Problems with "ada0: Previously was known as ad6" functionality Message-ID: <CAB%2BTj8-oUFC68YMYfcs=Kvtg-bPqi0myxo=KKGDbfsbZV3f5eA@mail.gmail.com> In-Reply-To: <7FE0AE74-7C29-4DD0-8EBA-F2BB70F3CB97@gmail.com> References: <CAB%2BTj8_oohsoPUokRfuyJSMzF%2B5FEgFaU_f2zdDjJ4UFk6CcBg@mail.gmail.com> <7FE0AE74-7C29-4DD0-8EBA-F2BB70F3CB97@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 25, 2011 at 4:35 PM, Nikolay Denev <ndenev@gmail.com> wrote: > I was struck with this problem too yesterday. > I was able to import the pool by specifying the directory where zpool should look for devices. > Like : zpool import -d /dev/gptid > Alternatively you can try putting kern.cam.ada.legacy_aliases=0 in your /boot/loader.conf Hello Nikolay, Thanks for your reply! The kern.cam.ada.legacy_aliases=0 indeed makes the /dev/ad6 device go away. However, unlike I suspected, it did not solve the zpool import problem. It still lists my pool as corrupted. If I use the zpool import -d /dev/gpt as you suggested, the pool displays as ONLINE and I can import it just fine. Using -d /dev works too, so I guess this works fine as a workaround. Still, can I assume this is a bug that will be fixed in time before 9.0-RELEASE ? Regards, Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB%2BTj8-oUFC68YMYfcs=Kvtg-bPqi0myxo=KKGDbfsbZV3f5eA>