From owner-freebsd-current@freebsd.org Thu Jan 4 11:15:00 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 93B0BEAA534 for ; Thu, 4 Jan 2018 11:15:00 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DA3963C49; Thu, 4 Jan 2018 11:14:59 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ldcv0-1fEfxV19Qw-00ilSr; Thu, 04 Jan 2018 12:14:55 +0100 Date: Thu, 4 Jan 2018 12:14:47 +0100 From: "O. Hartmann" 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: <20180104121447.4d9109ed@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> References: <20171231004137.4f9ad496@thor.intern.walstatt.dynvpn.de> <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:J4ASdeIuaRdvPxDD4+/L7VsgBlFbcJcXQLTE2rFFA/r8oS94Nja 5xNM6eDM3v4Qgzy84RYWHH1YbmLyDDaHgFKm2975ATFryNWJRWRS0MrNAaRhMixmcWufOL+ rtP9+SSDX8WRFhfDIDN1bQd5CvzhJQzLJB86o+HUWI2zVF3V363ohqsJjdpSMyhrFW+Y8tJ Jr5YLG87rtSml3js8pDvg== X-UI-Out-Filterresults: notjunk:1;V01:K0:mNDqVR2hFMc=:Z0RgrNKaJy9hu78V0pTwdK x0B6lUkMinjd8p8/SlhzpJqe9PfTmkt8IVSwqxNt4mQEEAl/KDadFkNrUQFFmJENXGq/6P4IQ ijZCzuPrKFxvnOj3G5bkqnJo7zfvpmy62lzOH7giy1/+7B0u8lo8Yy2TdqlflkqOcYbRm1bqJ prXwQv/lwUtRzrBiaWfSjY3touQvmzZfw81WWyBWeCYiUkW4nGuLe4JFg0V/O17vJkh8ST56l G6B+5tweygCCf1kNtyo9shEDiN/eey01Rdu4ftRIit5FCNc8wzRmEPmaLMjvZlwpD/7Pl694A itjaQDr9XjNNUHVXacRDwMySlflM2+oY/3/56hTlhCP3/AhObHEpTKYNjkHHujdW6lja5S3xz bhNTcOOmplfW+Jl0DTUGbejdBb/29uCLexs4Jhh+knwPXVQTbvdXD2rJ4Bk3DKA8wL09c6aTl B+rYGSgEX0BPkwtLrmCtg9L0OAL0yG2LD3euupcFpoaLFf6BiRGm9nuw0aTphDnSg9o/ZkMSB aWCY1awxN7pLKUgpWlqKcZSxll+D3z7gw9w/UDDtVfq+03Dgd8wFu4wTURWpnI8OaT/BSelWT bAW7pjtib4tSzTxYqZWe7j7+fc3BbjakyO+STfKxIYbpSrLdICIg+r9LVP2rKQ5nECeluxKfy 3UNoAlLWyeWuWFQhogV+3gNBG4HkzxaAIPQR4cWxFRZIwyIH5c6Ys6uL00OhSqaaHXmfmH4TW ehcPusJyMWYaDbYrxm7F94VxGBdhaNqgtVzOKgKhMsFLYoLqWn4e8Os4Xnbq7bFvckUGCtfLs JCXI3Y+132e79DasEFCqqh9WTCHec8deYtmoY6w+AeIISs6S30= 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 11:15:00 -0000 On Thu, 4 Jan 2018 09:10:37 +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. > > You can check using tunefs -p devname if soft update journaling is enabled or > not. In all cases I reported in earlier and now, softupdates ARE ENABLED on all partitions in question (always GPT, in my cases also all on flash based devices, SD card and/or SSD). > > Best regards > Michael > > > > 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" > > _______________________________________________ > 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"