From owner-freebsd-current@freebsd.org Thu Jan 4 08:10:42 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 2DC94EA633F for ; Thu, 4 Jan 2018 08:10:42 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E91727EDF0 for ; Thu, 4 Jan 2018 08:10:41 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [10.0.1.108] (unknown [212.201.121.94]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id B65767213BA4C; Thu, 4 Jan 2018 09:10:39 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 30 23:29:24 <0.2> From: Michael Tuexen In-Reply-To: Date: Thu, 4 Jan 2018 09:10:37 +0100 Cc: "O. Hartmann" , FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> References: <20171231004137.4f9ad496@thor.intern.walstatt.dynvpn.de> To: Warner Losh X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de 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: Thu, 04 Jan 2018 08:10:42 -0000 > On 31. Dec 2017, at 02:45, Warner Losh wrote: >=20 > On Sat, Dec 30, 2017 at 4:41 PM, O. Hartmann = wrote: >=20 >> On most recent CURRENT I face the error shwon below on /tmp = filesystem >> (UFS2) residing >> on a Samsung 850 Pro SSD: >>=20 >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: = 0x4515d2a3 !=3D >> bp: 0xd9fba319 >> handle_workitem_freefile: got error 5 while accessing filesystem >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: = 0x4515d2a3 >> !=3D bp: 0xd9fba319 >> handle_workitem_freefile: got error 5 while accessing filesystem >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: = 0x4515d2a3 >> !=3D bp: 0xd9fba319 >> handle_workitem_freefile: got error 5 while accessing filesystem >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: = 0x4515d2a3 >> !=3D bp: 0xd9fba319 >> handle_workitem_freefile: got error 5 while accessing filesystem >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: = 0x4515d2a3 >> !=3D bp: 0xd9fba319 >> handle_workitem_freefile: got error 5 while accessing filesystem >>=20 >> I've already formatted the /tmp filesystem, but obviously without any >> success. >>=20 >> Since I face such strange errors also on NanoBSD images dd'ed to SD = cards, >> I guess there >> is something fishy ... >=20 >=20 > 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. You can check using tunefs -p devname if soft update journaling is = enabled or not. Best regards Michael >=20 > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"