From owner-freebsd-current@freebsd.org Wed Jul 12 22:37:56 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0DCCDA69B0 for ; Wed, 12 Jul 2017 22:37:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-71.reflexion.net [208.70.210.71]) (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 8908E7A897 for ; Wed, 12 Jul 2017 22:37:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29683 invoked from network); 12 Jul 2017 22:31:15 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 12 Jul 2017 22:31:15 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Wed, 12 Jul 2017 18:31:15 -0400 (EDT) Received: (qmail 18222 invoked from network); 12 Jul 2017 22:31:15 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Jul 2017 22:31:15 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6861AEC8936; Wed, 12 Jul 2017 15:31:14 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: dump trying to access incorrect block numbers? From: Mark Millard In-Reply-To: Date: Wed, 12 Jul 2017 15:31:13 -0700 Cc: FreeBSD Current , linimon@FreeBSD.org Content-Transfer-Encoding: 7bit Message-Id: References: <73E92033-CB2F-404C-8B3F-736EF09AA9F7@dsl-only.net> To: peter@rulingia.com, Michael Butler , "Rodney W. Grimes" X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Jul 2017 22:37:57 -0000 I have extracted material from the list-exchanges related to this and submitted: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220693 against the kernel for the issue. I placed emphasis on the SSD-trim related "freeing free block" panics that "fsck -B" can lead to after it gets the g_vfs_done messages for unclean ufs file systems but first noted that: mksnap_ffs /.snap2 was enough to get the g_vfs_done messages. I figured that the nastiest and most important known consequences were "fsck -B" being broken for unclean ufs file systems and having later panics trying to trim based on how it is broken. I did also mention dump as producing the messages. I referenced. . . > See also the exchange of list submittals associated > with: > > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066505.html > > and: > > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066508.html === Mark Millard markmi at dsl-only.net