From owner-freebsd-current@freebsd.org Mon Jan 8 15:34:04 2018 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 BB040E72CE0 for ; Mon, 8 Jan 2018 15:34:04 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 713FE805C6; Mon, 8 Jan 2018 15:34:04 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id d202so14582741qkc.9; Mon, 08 Jan 2018 07:34:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=5b5V6cFgy6ZWoPf+4544dBDTC02mL32l+3WCWbDFCJQ=; b=c4XnT0agqaS9D6Ika+exDEWD5fp9Ox/XMljITGfZ6JTSkjlCNbxVo0qeDzSNp8bUKM dd4LykfADngkp/b/umtQuoU3FRj4h3uKD92We75FmPpYHXJLesRRYSWNieFgD38K+UQV UOlGlDAQcm3RjSEUmtth1S8kLG+0V3+Uhcdks7j/D8AuI/wsaJezs/mn7w9l6b3VQ62p /uTpPZjFs9z9lWZTZ3zxaVh7u87V7uMAjAnis40DFIMdPpETsp9SpXiuspqimNkcgxG/ LTW9qMKhdPNgRBITha758WJQp4R80BgCdcI9H2BLUFvC4GQeZO1XeUv+TVdbQZSy5o/D g6Bw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=5b5V6cFgy6ZWoPf+4544dBDTC02mL32l+3WCWbDFCJQ=; b=D3mGKJOaci37jVQqNc/zxFOpANZPytSS1poiKIkzuDhH1nHUGN48PvpfiKNHMHY0uh 8P+nAlimveU1wXPq1+dZBVnuu2MpT62XC4dDWF6kamDgwKxBSiDTlN3ksGNBbBHlM68b Lr3SR8C42pjNdOOGVdlH1C6DbXVtYSO7BJaZaijYiTrBBDQIvaaW9A3I5jGDDGPpjgLS 7oYce1maUwoCkMdqJ61KMs8SNA96GOZeltGr7e5Q1sgdyoGBmti+JDmT8tX9PNL5PJ0/ 1yM2K0EzJLoX2yxYRFVLBqKUR7Tq7hRB6QRfq6bsiHyWSr2OJ0dsnJ9j6DbZEZvycNH6 fJug== X-Gm-Message-State: AKwxytfslaNAlsesoqYSHfHD2q5VEkjnj2HvqyWUYLPZoVHVf9+7pEuQ X4eQrmdrET6pq7dCD5y4lrmw5Q== X-Google-Smtp-Source: ACJfBotP0EVR9A3O3tJx+lTmcUCq4MiPKvD1z4h3pGBIrpRPtaxj0focRttP+a19WEPXOIS3Wn4Itw== X-Received: by 10.55.15.2 with SMTP id z2mr16982253qkg.91.1515425642653; Mon, 08 Jan 2018 07:34:02 -0800 (PST) Received: from raichu (toroon0560w-lp140-02-70-49-169-112.dsl.bell.ca. [70.49.169.112]) by smtp.gmail.com with ESMTPSA id p8sm7757231qtj.70.2018.01.08.07.34.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jan 2018 07:34:01 -0800 (PST) Sender: Mark Johnston Date: Mon, 8 Jan 2018 10:33:56 -0500 From: Mark Johnston To: Michael Tuexen Cc: Warner Losh , "O. Hartmann" , FreeBSD CURRENT Subject: Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 30 23:29:24 <0.2> Message-ID: <20180108153356.GA2412@raichu> References: <20171231004137.4f9ad496@thor.intern.walstatt.dynvpn.de> <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Mon, 08 Jan 2018 15:34:04 -0000 On Thu, Jan 04, 2018 at 09:10:37AM +0100, Michael Tuexen wrote: > > On 31. Dec 2017, at 02:45, Warner Losh wrote: > > > > On Sat, Dec 30, 2017 at 4:41 PM, O. Hartmann wrote: > > > >> On most recent CURRENT I face the error shwon below on /tmp filesystem > >> (UFS2) residing > >> on a Samsung 850 Pro SSD: > >> > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 != > >> bp: 0xd9fba319 > >> handle_workitem_freefile: got error 5 while accessing filesystem > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 > >> != bp: 0xd9fba319 > >> handle_workitem_freefile: got error 5 while accessing filesystem > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 > >> != bp: 0xd9fba319 > >> handle_workitem_freefile: got error 5 while accessing filesystem > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 > >> != bp: 0xd9fba319 > >> handle_workitem_freefile: got error 5 while accessing filesystem > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 > >> != bp: 0xd9fba319 > >> handle_workitem_freefile: got error 5 while accessing filesystem > >> > >> I've already formatted the /tmp filesystem, but obviously without any > >> success. > >> > >> Since I face such strange errors also on NanoBSD images dd'ed to SD cards, > >> I guess there > >> is something fishy ... > > > > > > It indicates a problem. We've seen these 'corruptions' on data in motion at > > work, but I hacked fsck to report checksum mismatches (it silently corrects > > them today) and we've not seen any mismatch when we unmount and fsck the > > filesystem. > Not sure this helps: But we have seen this also after system panics > when having soft update journaling enabled. Having soft update journaling > disabled, we do not observed this after several panics. > Just to be clear: The panics are not related to this issue, > but to other network development we do. I saw the same issue this morning on a mirrored root filesystem after my workstation came up following a power failure. fsck recovered using the journal, and I subsequently saw a number of these checksum failures. Upon shutdown, I saw the same handle_workitem_freefile errors as above. I then ran a full fsck from single-user mode, which didn't turn up any inconsistencies, and after that the checksum failure errors disappeared, presumably because fsck fixed them.