Date: Thu, 28 Apr 2016 13:58:01 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit.kuehn@aei.mpg.de> To: Karli =?ISO-8859-1?Q?Sj=F6berg?= <karli.sjoberg@slu.se> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: zfs on nvme: gnop breaks pool, zfs gets stuck Message-ID: <20160428135801.7eed38d20cd975a7d67c9283@aei.mpg.de> In-Reply-To: <1461822768.16231.6.camel@slu.se> References: <20160427152244.ff36ff74ae64c1f86fdc960a@aei.mpg.de> <20160427141436.GA60370@in-addr.com> <20160428074846.a28da3113294f1edc6ed9ce6@aei.mpg.de> <1461822768.16231.6.camel@slu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28 Apr 2016 05:52:48 +0000 Karli Sj=F6berg <karli.sjoberg@slu.se> wrote about Re: zfs on nvme: gnop breaks pool, zfs gets stuck: > > I still wonder why the gnop workaround went so terribly wrong.=20 KS> Again, because you need to tell zfs where the providers are: KS> # zpool import -d /dev/gpt flash ? Never needed to do that before, and why would it miss only 2 out of 3 device nodes that are all located in gpt? And why would it hang instead of giving an error message? cu Gerrit
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160428135801.7eed38d20cd975a7d67c9283>