Date: Fri, 08 May 2020 13:54:55 -0300 From: Joseph Mingrone <jrm@FreeBSD.org> To: Toomas Soome <tsoome@me.com> Cc: Steve Wills <swills@FreeBSD.org>, questions@freebsd.org, Kyle Evans <kevans@freebsd.org>, Toomas Soome <tsoome@freebsd.org>, Allan Jude <allanjude@freebsd.org> Subject: Re: ZFS system can no longer boot - zfs_alloc()/zfs_free() mismatch Message-ID: <86tv0qpdsw.fsf@phe.ftfl.ca> In-Reply-To: <8E6AE59B-4318-431E-A063-902BA0095262@me.com> (Toomas Soome's message of "Fri, 8 May 2020 17:32:27 %2B0300") References: <CANRUcdAtNWdMMoSYmZ27NEFgPQTF7-KFdBXBTy6JmuDxG8edUw@mail.gmail.com> <ac07ac9b-ce3a-ab05-a95f-b1e4c4fd88d2@FreeBSD.org> <53F8CCBC-80EA-4CC6-9775-1E50B3D18D4A@me.com> <86zhaia6xo.fsf@phe.ftfl.ca> <8E6AE59B-4318-431E-A063-902BA0095262@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Toomas Soome <tsoome@me.com> writes: >> On 8. May 2020, at 16:32, Joseph Mingrone <jrm@FreeBSD.org> wrote: >> Toomas Soome <tsoome@me.com <mailto:tsoome@me.com>> writes: >>>> On 8. May 2020, at 16:13, Steve Wills <swills@FreeBSD.org> wrote: >>>> I didn't solve it, I avoided it by renaming the kernel directory and r= einstalling the kernel, forcing the bits to be in a different physical loca= tion on disk... The only theory I had at the time was that the bits were be= yond some arbitrary 4G limit or something, but that was just a wild idea. G= ood luck, that's super frustrating. >>>> Steve >>> I guess we better backport the zfs_alloc/zfs_free removal code=E2=80=A6= You can use loader from current meanwhile. >>> rgds, >>> toomas >> We tried loader/zfsloader from current, but the got the same error. >> Joe > That is not quite possible as current has zfs_alloc() and zfs_free() remo= ved and we use malloc()/free() instead. > rgds, > toomas After using a loader from current (2020-04-10) *and* linking zfsloader to i= t, the error is: panic: free: guard2 fail @ 0xd1e054a0 + 13 from unknown:0 Also tried with Allan's CURRENT gptzfsboot and the panic was the same. Joe >>>> On 5/7/20 7:59 PM, Joseph Mingrone wrote: >>>>> Hello everyone, >>>>> As it says in the subject line, my system stopped booting for some >>>>> unknown reason. It might have been after upgrading from 12.1-p2 to >>>>> -p4, but I'm unsure. It sounds similar to this issue: >>>>> https://twitter.com/alelab_/status/1222437570501644291 >>>>> Allan and I tried debugging for a few hours today, but without >>>>> success. We tried replacing the boot code and the loaders, but the >>>>> result was the same. We also tried booting from a usb thumb drive, >>>>> then `set currdev=3Dzfs:zroot/ROOT/default:` and `boot`, but the same >>>>> error is shown. >>>>> Steve and Kyle, did you ever solve this problem? >>>>> Thanks, >>>>> Joe --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKkBAEBCgCOFiEEVbCTpybDiFVxIrrVNqQMg7DW754FAl61jt9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUQHGpybUBmcmVl YnNkLm9yZwAKCRA2pAyDsNbvnp5lD/9bEk2fy2K8yAebGizVJG7W1oBh3hdtUxDT JcNkws4ns1An3E9bJILM9VgwM07bc0p0letGlidecT3ANRYtFSv1cmrgoMNMJ5r6 oLl8Fb3h0F+Cd7nySZ2LvG9SnhOuVd7UEVHoxSJbkrNtgQVY4vTRb2Y9vJwkx9J2 5i020XuyK8qm3DCpWUOlUENyRRjH6O0svNH3Mkfwo27jTMEB626QLBNJAmSicr1x KUQqnomPReASk3LVciwJyd8a6spkYetCrDefhyih9E4OlmWN9p35Mr98jAbc/BOl XcFhYy1BG68gtWHFLX1c09c7M9kQENG8cHVM0CpGK5Dm9XmOnkFRGqZNwyCLIMAE lJBg3RQhDG6nfOL3kH3UJVZwqPoACuRk2TJFM10bbOO1uzN+tsoRLwIS9amxPq3p DZOkfqP7ZswCNPXc+R2kYC7ngeB6EzHC7rRZAy5TJZT2ymHHykJFeRzo6MdMNNAl hKbaoP6rBxx8uMCwAtLnbB93rD8rM+0Hn4Pa1WHn6HaUoyD+w/JAoM12+mTnAylx e3OSd3CB+4n9XSU9i0PofsFiVwS5tWmsO/r535uxtSeIE5jQOZJS45qrvTS6d6n1 xzXP0Zu2VuZDSkihXGP8dAhIZd5LR7pXUYRwZXm4kl3+OYaHsOVA9FLksYr9/5k9 1fHzdkmKDQ== =eMzk -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86tv0qpdsw.fsf>