Date: Sat, 19 Aug 2023 12:55:46 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: Dimitry Andric <dim@freebsd.org> Cc: freebsd-current@freebsd.org Subject: ZFS deadlock in 14: with ZIL :-) Message-ID: <174925b2-e8ba-2da0-7dfd-d062e303c53a@gmail.com> In-Reply-To: <23BA44D4-8F35-4A0A-87A2-F765FE6D6865@FreeBSD.org> References: <59FCB309-4A55-4924-98C4-7ACCA70FD299.ref@yahoo.com> <59FCB309-4A55-4924-98C4-7ACCA70FD299@yahoo.com> <9ba2326b-d5de-5faa-edc8-b1cd7235a51c@gmail.com> <23BA44D4-8F35-4A0A-87A2-F765FE6D6865@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/08/2023 11:31, Dimitry Andric wrote: > On 19 Aug 2023, at 09:36, Graham Perrin <grahamperrin@gmail.com> wrote: >> … >> >> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271945#c0>; no ZIL; I never used the feature. > The ZIL always exists, but it can be stored on a separate device for > performance reasons. See zpoolconcepts(7), the Intent Log section: > > By default, the intent log is allocated from blocks within the main pool. > However, it might be possible to get better performance using separate > intent log devices such as NVRAM or a dedicated disk. For example: > # zpool create pool sda sdb log sdc > > -Dimitry Thanks! I looked at the page umpteen times, that part never sunk in. Now I know. <https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html#Intent_Log>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?174925b2-e8ba-2da0-7dfd-d062e303c53a>