Date: Sun, 3 Nov 2019 20:42:53 -0500 From: Alexander Motin <mavbsd@gmail.com> To: d@delphij.net, Ravi Pokala <rpokala@freebsd.org>, Toomas Soome <tsoome@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r354283 - in head: stand/libsa/zfs sys/cddl/boot/zfs Message-ID: <cb846ed5-319f-7ef6-0604-047c5f3009b5@gmail.com> In-Reply-To: <61bed957-a0c5-bb95-8138-13d00df9d44f@delphij.net> References: <201911031325.xA3DPl3B080386@repo.freebsd.org> <AC86E653-444A-4EBD-8379-BBA53BD160D3@panasas.com> <61bed957-a0c5-bb95-8138-13d00df9d44f@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03.11.2019 20:19, Xin Li wrote: > On 2019-11-03 15:30, Ravi Pokala wrote: >> Uh.... >> >> I've had a log device in my boot-pool for months, and have booted without issue: >> >> [threepio:~] rpokala% zpool status zroot >> pool: zroot >> state: ONLINE >> scan: scrub repaired 0 in 0 days 00:04:36 with 0 errors on Mon Oct 28 03:10:59 2019 >> config: >> >> NAME STATE READ WRITE CKSUM >> zroot ONLINE 0 0 0 >> nvd1p4 ONLINE 0 0 0 >> logs >> nvd0p1 ONLINE 0 0 0 >> >> errors: No known data errors > > > This is not supported, and it's not trivial to support it, because in > order to support it, the bootloader would have to know how to replay > zilogs, which would add quite a lot of code to it. The issue with ZIL not being replayed in case of read-only mount has nothing to do with the fact of SLOG device presence. The issue is the same when ZIL resides on the main disks of the pool. So while everything else you said is right, I see no any reason to ban pools with SLOG devices in this context. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb846ed5-319f-7ef6-0604-047c5f3009b5>