From owner-freebsd-current@freebsd.org Thu Dec 13 23:34:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B303D1338486 for ; Thu, 13 Dec 2018 23:34:59 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [70.36.157.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDA4377696 for ; Thu, 13 Dec 2018 23:34:58 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost [IPv6:::1]) by chez.mckusick.com (8.15.2/8.15.2) with ESMTP id wBDNihMV064694; Thu, 13 Dec 2018 15:44:43 -0800 (PST) (envelope-from mckusick@mckusick.com) Message-Id: <201812132344.wBDNihMV064694@chez.mckusick.com> From: Kirk McKusick To: gljennjohn@gmail.com Subject: Re: enabling inode hashes results in kernel panics cc: Cy Schubert , freebsd-current@freebsd.org X-URL: http://WWW.McKusick.COM/ Reply-To: Kirk McKusick In-reply-to: <20181213180811.14ef0c75@ernst.home> Comments: In-reply-to Gary Jennejohn message dated "Thu, 13 Dec 2018 18:08:11 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <64692.1544744683.1@chez.mckusick.com> Date: Thu, 13 Dec 2018 15:44:43 -0800 X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,MISSING_MID, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on chez.mckusick.com X-Rspamd-Queue-Id: CDA4377696 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.25 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[mckusick@mckusick.com]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.82)[0.820,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[mckusick.com]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: chez.mckusick.com]; RCVD_IN_DNSWL_NONE(0.00)[235.157.36.70.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_MEDIUM(-0.09)[-0.088,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:46375, ipnet:70.36.128.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.38)[ip: (-0.66), ipnet: 70.36.128.0/19(-0.33), asn: 46375(-0.81), country: US(-0.09)] X-Mailman-Approved-At: Fri, 14 Dec 2018 00:19:36 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2018 23:34:59 -0000 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