Date: Thu, 13 Dec 2018 15:44:43 -0800 From: Kirk McKusick <mckusick@mckusick.com> To: gljennjohn@gmail.com Cc: Cy Schubert <Cy.Schubert@cschubert.com>, freebsd-current@freebsd.org Subject: Re: enabling inode hashes results in kernel panics Message-ID: <201812132344.wBDNihMV064694@chez.mckusick.com> In-Reply-To: <20181213180811.14ef0c75@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
As the person resposible for ading the inode check-hashes, sorry for the problems that they are causing you. Gary, I may want your crash dumps and the core.txt files, but let me do some preliminary investigation of fsck to see if I can figure out why it is failing to fix the inode check-hashes. Are you running with soft updates or journaled soft updates? Is the problem that fsck is not finding that are are bad check-hashes, or is fsck finding them and not fixing them? Since fsck and fsdb share the same code for reading and updating inodes, it is odd that fsdb fixes the check-hashes, but the same code running in fsck does not. Kirk McKusick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201812132344.wBDNihMV064694>