Date: Thu, 28 Apr 2016 07:27:23 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit.kuehn@aei.mpg.de> To: Gary Palmer <gpalmer@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: zfs on nvme: gnop breaks pool, zfs gets stuck Message-ID: <20160428072723.9871ac9ede56ebbbc17ee734@aei.mpg.de> In-Reply-To: <20160427141436.GA60370@in-addr.com> References: <20160427152244.ff36ff74ae64c1f86fdc960a@aei.mpg.de> <20160427141436.GA60370@in-addr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Apr 2016 15:14:36 +0100 Gary Palmer <gpalmer@freebsd.org> wrote about Re: zfs on nvme: gnop breaks pool, zfs gets stuck: GP> Did you destroy the gnop devices with the pool online? In the GP> procedure I remember you export the pool, destroy the gnop devices, GP> and then reimport the pool. Yes, I exported the pool before destroying the gnop devices. That's why I was wodering about what is happening. GP> vfs.zfs.min_auto_ashift GP> GP> which lets you manage the ashift on a new pool without having to try GP> the gnop trick That's a great hint I didn't know about. I'll try this, thanks! cu Gerrit
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160428072723.9871ac9ede56ebbbc17ee734>