From owner-freebsd-current@freebsd.org Fri Jun 21 20:27:13 2019 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 C73B415BE797 for ; Fri, 21 Jun 2019 20:27:13 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 3C03D77D34; Fri, 21 Jun 2019 20:27:13 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 849BB22302; Fri, 21 Jun 2019 16:27:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 21 Jun 2019 16:27:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsco.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=B Z1AbgDR2eQtWW3MMPU2crVv3ck58j6cAF8/T5+K31I=; b=LdTZxruP9BwfNOuZn yim7s59Bm8ZlI5DuHTkDQ0njn60KbKPAc9rXku3jhM1iRJDM7/VeLt9IIDTz+ZVB O8tOQYWfh6oE7nS+myWQrnbCEc0lYqe9z/j1Jyr+tZWDf7UUw5pLNo9C7GvVKC08 6236RJY0Nj2LczLiR60GZkqoGomRM23/3VMd52ME8XGjMx+iJ9fSK7PUy2jzrlOe 6cXsLty7z2pdRYoSxmRx8ksDY/VuL0l3FN7XQh2aS77bTndBhHjXo5BbQMXNsdeU d2IN31pcGfKqGG7F2Sshe/N9KJh8srxxNlIgsSBKApNEbtcOob8flAn8fCecWUxh Cmwgw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=BZ1AbgDR2eQtWW3MMPU2crVv3ck58j6cAF8/T5+K3 1I=; b=qBM57pKYpaFDJk88dPLMz2wxeZdq18Jk2NDWIjUva5kzqqCKmCs/46/0k 4tRm4/N1AyQBhldYmYUrlGi5AJ18AFR1VoPf2G1Xw1XicMJkiyPoFtZyrDpItH9g QDKX97xibw5YZGYyy5wWIRop/uXFkFKmCSEwMGBDwlKHuuhTHPjKjEXoZL+VIAC2 +OtI0naVhtnWpkWAScq3X16rWpjmCLsPFkS6NcyhdxKMDeOXmPIYscgBXWIbPPrH 2V5pktaiGGO18RID2ULR8IA8M7gg6RmBU2UkPZ2OTXOKumItVglDbzvETjQVwwA2 S1CF1zlS84884wem7O37/k3Q68g0w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrtdeigdduheefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhepufgtohht thcunfhonhhguceoshgtohhtthhlsehsrghmshgtohdrohhrgheqnecukfhppeduledvrd ehhedrheegrdehleenucfrrghrrghmpehmrghilhhfrhhomhepshgtohhtthhlsehsrghm shgtohdrohhrghenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from [10.178.24.13] (unknown [192.55.54.59]) by mail.messagingengine.com (Postfix) with ESMTPA id 141368005A; Fri, 21 Jun 2019 16:27:10 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Reducing UFS corruption from unclean shutdowns? From: Scott Long In-Reply-To: Date: Fri, 21 Jun 2019 14:27:09 -0600 Cc: FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Alan Somers , Chuck Silvers , Kirk McKusick X-Mailer: Apple Mail (2.3445.104.11) X-Rspamd-Queue-Id: 3C03D77D34 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=samsco.org header.s=fm3 header.b=LdTZxruP; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=qBM57pKY; spf=pass (mx1.freebsd.org: domain of scottl@samsco.org designates 66.111.4.28 as permitted sender) smtp.mailfrom=scottl@samsco.org X-Spamd-Result: default: False [-5.62 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[samsco.org:s=fm3,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.28]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_NA(0.00)[samsco.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[samsco.org:+,messagingengine.com:+]; MX_GOOD(-0.01)[cached: in2-smtp.messagingengine.com]; NEURAL_HAM_SHORT(-0.98)[-0.980,0]; IP_SCORE(-3.53)[ip: (-9.80), ipnet: 66.111.4.0/24(-4.74), asn: 11403(-3.07), country: US(-0.06)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[28.4.111.66.list.dnswl.org : 127.0.5.1] 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: Fri, 21 Jun 2019 20:27:14 -0000 > On Jun 21, 2019, at 2:09 PM, Alan Somers wrote: >=20 > On Fri, Jun 21, 2019 at 1:56 PM Scott Long wrote: >>=20 >>=20 >>=20 >>> On Jun 21, 2019, at 1:49 PM, Alan Somers = wrote: >>>=20 >>> I panic my development VM regularly. Each time, I need to fsck the >>> file system. Even if I had run sync(8) just before the panic, I >>> frequently find corruption. What should I change to make sync(8) >>> work, or at least to make corruption rare? It looks like my root = file >>> system is using soft-updates+journal. Should I disable those? >>>=20 >>=20 >> What corruption do you regularly see? >>=20 >> Scott >=20 > fsck reports various types of errors, all repairable, like "INODE > CHECK-HASH FAILED", "FREE BLK COUNT(S) WRONG IN SUPERBLK", "SUMMARY > INFORMATION BAD", "BLK(S) MISSING IN BIT MAPS", and "UNREF FILE". If > I don't run fsck, then I get errors when I try to access files. Like > "inode XXX: check-hash failed" and "such and such is marked as an > executable file but could not be run by the operating system". > -Alan The freeblk count and summary information messages are normal and = expected. I don=E2=80=99t think that the blks missing message is expected, and the = unref file message is definitely a red flag of something that should have been handed with = journal recovery. Kirk and Chuck, do you have any insight here? Thanks, Scott