Date: Sun, 3 Nov 2019 17:19:03 -0800 From: Xin Li <delphij@delphij.net> To: 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: <61bed957-a0c5-bb95-8138-13d00df9d44f@delphij.net> In-Reply-To: <AC86E653-444A-4EBD-8379-BBA53BD160D3@panasas.com> References: <201911031325.xA3DPl3B080386@repo.freebsd.org> <AC86E653-444A-4EBD-8379-BBA53BD160D3@panasas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1Ml20wRaSfzcucOS3LgU7nPfd3XfKe7Dv Content-Type: multipart/mixed; boundary="2UUtBCh5AT5UmyB9XvkIYRjoIhlAN89vO"; protected-headers="v1" From: Xin Li <delphij@delphij.net> Reply-To: d@delphij.net To: Ravi Pokala <rpokala@freebsd.org>, Toomas Soome <tsoome@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Message-ID: <61bed957-a0c5-bb95-8138-13d00df9d44f@delphij.net> Subject: Re: svn commit: r354283 - in head: stand/libsa/zfs sys/cddl/boot/zfs References: <201911031325.xA3DPl3B080386@repo.freebsd.org> <AC86E653-444A-4EBD-8379-BBA53BD160D3@panasas.com> In-Reply-To: <AC86E653-444A-4EBD-8379-BBA53BD160D3@panasas.com> --2UUtBCh5AT5UmyB9XvkIYRjoIhlAN89vO Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable (chosen a random message) On 2019-11-03 15:30, Ravi Pokala wrote: > Uh.... >=20 > I've had a log device in my boot-pool for months, and have booted witho= ut issue: >=20 > [threepio:~] rpokala% zpool status zroot > pool: zroot > state: ONLINE > scan: scrub repaired 0 in 0 days 00:04:36 with 0 errors on Mon Oc= t 28 03:10:59 2019 > config: >=20 > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > nvd1p4 ONLINE 0 0 0 > logs > nvd0p1 ONLINE 0 0 0 >=20 > 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. It's unlikely that you actually hit a problem, however, because the critical contents to boot the system is rarely written to, and as a result it's quite likely that the readable, consistent state of your /boot/ is good enough to boot the system. That's said, it's still because you were lucky, and the code was not designed to work that way...= Cheers, --2UUtBCh5AT5UmyB9XvkIYRjoIhlAN89vO-- --1Ml20wRaSfzcucOS3LgU7nPfd3XfKe7Dv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.2.17 (FreeBSD) iQIzBAEBCgAdFiEEceNg5NEMZIki80nQQHl/fJX0g08FAl2/fIwACgkQQHl/fJX0 g0+GTA/8CqC8u5dDZJVA10LrU6KpQqZqx9ZuTm8o3Kdgm+lei+MMMMKYlng5ugBc iW8ko8k1ElIPk8BuYqnv0F3r6IoHxIU7Wn9vQK9DqVl3R+QDR9OdgZOLrTu5zJhG q3tDyQ0fHFPtmOaKJJcnu/d8qZZMZXPiMCAk+3ZbjskmVlDqhOwHMSF4NuX+wuFW pJo6c0u79VedvU3wBdDcCv1Y4X4Sjq08pcdLOV7iaG/O/JPP66nLyfrWrY1SLzGp eNJ0h8DgHVdbsgf4MyuwMVkb0MMNQx8juXEk+ovKJaZkwFwswLfyG6fOeAWyr6IH O0Iolm3ocCnYyncKM63BoEkatosLl75vet9ke1gRpxEWB+NXHQOKgbMEiPWsReVQ wOFN2VgoT8M0zB8u3WexZuIoUMY76s8KVL/ND3kBP/fSE85CXyiWY2nR7Q/WuDBf 9DSakJckexaGG6uPnrmkvBFN7eFsLQG7s4sir9TA3k1ET0rILO5SOoD8/A9ZrQXi Coc8ZvmZVV35RGSMZzaixuVKXGsaihfd84b4lmkTDmf4MVnct1nKuet1D6D0Td15 Y1+Fq+cLIHL9wggUoRquKMdzsbjg4lHKAWvw7D07MEf6FQkPBQgY158GBV+sRFTh 6BRWW0negOkmXUlmJeSsgqhv/uGDxwq6XoJPO3wzERa7+1QNIys= =PQAz -----END PGP SIGNATURE----- --1Ml20wRaSfzcucOS3LgU7nPfd3XfKe7Dv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61bed957-a0c5-bb95-8138-13d00df9d44f>