Date: Thu, 06 Nov 2014 21:10:56 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: Borja Marcos <borjam@sarenet.es> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS bug: was creating ZIL ignores vfs.zfs.min_auto_ashift, should be ZIL sets improper ashift with AHCI controllers Message-ID: <545BE3E0.4030203@multiplay.co.uk> In-Reply-To: <21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es> References: <B731A922-3F83-4D8E-A4EA-22C5CA8A3850@sarenet.es> <9C91F97841BC4347910F206618BAA3BB9AF327D1@PAIMAIL.pai.local> <545B76EF.6050709@multiplay.co.uk> <21D2A3A9-B6C1-458F-B17F-480251E999AE@sarenet.es>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/11/2014 14:58, Borja Marcos wrote:
> On Nov 6, 2014, at 2:26 PM, Steven Hartland wrote:
>
>> That's not relevant as min when set should override the drives params
> There is more to this than it seems, I just found more funny stuff.
>
> MY CONCLUSION IS: when creating a ZIL device, it behaves differently depending on the disk controller. It works with SAS,
> and it doesn't work with AHCI.
>
Ok narrowed down the issue, looks like cache file generation is where
the issue is, possibly a race condition.
If you run the following then rerun your zdb I suspect you'll get the
right results (ashift: 12)
zpool set cachefile='' <pool>
Alternatively you can run the following to display real pool config vs
that which is in the cache file:
zdb -C <pool>
Regards
Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?545BE3E0.4030203>