Date: Thu, 04 Oct 2018 01:10:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 192097] zpool status -x reports wrong information Message-ID: <bug-192097-227-N9Q6TDSQYz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192097-227@https.bugs.freebsd.org/bugzilla/> References: <bug-192097-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192097 Allan Jude <allanjude@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Works As Intended --- Comment #1 from Allan Jude <allanjude@FreeBSD.org> --- It is a configuration error however. Using 512b for 4k devices will cause performance degradation because of the read-modify-write that the hardware will have to do for every 512b write. I don't think it makes sense to locally modify the behaviour of ZFS in this instance. Hopefully we will eventually get the "Time Variable Geometry" feature for ZFS that will allow all future allocations to be made 4k aligned, even in the face of pools created on older versions of FreeBSD where we didn't have quirks in place on some disks that lie about their sector size. Video and Slides about the feature. "Oh Shift!" https://www.youtube.com/watch?v=_-QAnKtIbGc https://drive.google.com/file/d/0B5fzqkw_-diCZFVTZlpua3hjNWs/view?usp=sharing -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192097-227-N9Q6TDSQYz>