From owner-freebsd-current@freebsd.org Sun Jan 7 11:32:13 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 78FF2E674D7 for ; Sun, 7 Jan 2018 11:32:13 +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 EE59D823D9; Sun, 7 Jan 2018 11:32:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.181.255.64]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LzKQf-1eug6D2cYj-014TxE; Sun, 07 Jan 2018 12:32:08 +0100 Date: Sun, 7 Jan 2018 12:31:34 +0100 From: "O. Hartmann" To: "O. Hartmann" Cc: Michael Tuexen , Warner Losh , FreeBSD CURRENT Subject: Re: r327359: cylinder checksum failed: cg0, cgp: 0x4515d2a3 != bp: 0xd9fba319 Dec 30 23:29:24 <0.2> Message-ID: <20180107123201.19ea0fde@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180104121447.4d9109ed@freyja.zeit4.iv.bundesimmobilien.de> References: <20171231004137.4f9ad496@thor.intern.walstatt.dynvpn.de> <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> <20180104121447.4d9109ed@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ZmNi6G2KhPSkwUp9=voe_7f"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:8uYr4Zuh0Ufb4//Yb4R8izn7r2WGeO+U9nwAoIpxNDLX9CIuFA6 h4eDlBfvDi3bhDQw5OqHZtdcoFQdzejI+DMMOhj/a72QZ9aFTFENjI0SdsRyP7wHmQdzaql 8Qz3uui0PyJ9uSPUp0z1q8XtpkMolvTx003kzO3B+EzWQvDEy0bZtdafzzxb4khIxMdLJjc Nkh0/5B3vx0SkbM3iMRtQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:TH6GYwudZ0k=:yqTRlAZw0wrg08Gqpe16w7 kyJn5AoRViZ3HgPlJjzug+/yYTdQgV5BNfYOQpSWhxa09wPHfd5ziXHSheZRUfqqbtaRINUU2 tVbXp6+UumYqoVMwgjmar3IpiCFsTek2VmLaajB72mmseXDTIN/+ujw2U3tVkhJEo5GH/le3y AwldE6HxnDC4AMvw5sV7+NzCMXu9DxoxZXnwjeK2129jhfl2gkXiJIIvAdnTKOei2xWocrDUk 52L/3GgDsVWSGtbmdfjbAl1joJvQNi5/Lwh9BMRZbMJ7k37YE5Q8Uu0BJjBfarjjITHwaZ3wb YByAQMDC36pVSo2UBhRy4aMpdeB16x9HKg7tl/oea2n12B9KA1dun9BH+XKGtvzRIVj8qR1q+ OvJWEU0wDIEPg5MWbwJii/tVIIf0pUTtFxDn3WKhUiwiTj+s0wgnsw+UIs/WxADvwN+cvyQ1l Dw6ONw3in4kTZ5VnN67PBe/ij5pQsed/W5O0CoIoPn+PUG8mBPi4nz0h45i3azgvQF/+j0DRQ EY/Vt8xmb+XF0EkV94jlFXTNMKfLZhmyxBgA0bNHdQoenOGD45tPLC2FkKvt8hCM/wPlZlvF/ lfvx0pcImlcPtRHvhiLRLacr4vJwzaAFjgzL6OwexvpZBCoYyYsVXA1vTi84Ez+zxl4reeNyI gH6jHhetQv3u5X6ec5gH0mpl3oKkiwSA8cSjP2ScEZwkUphSLPng2/Y56AisyXVoGaNNwXLwa 1+aEXDivOm8RmpLDrMh9T6M8GScRGVbjKgUGFDOiP19eL9zalJ0RrSHo0WrnADNbxoBqn2HHE CS49RioH4fDY6xX4mx2f4ZpGAmrZA== 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: Sun, 07 Jan 2018 11:32:13 -0000 --Sig_/ZmNi6G2KhPSkwUp9=voe_7f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Thu, 4 Jan 2018 12:14:47 +0100 "O. Hartmann" schrieb: > On Thu, 4 Jan 2018 09:10:37 +0100 > Michael Tuexen wrote: >=20 > > > 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 filesyst= em > > >> (UFS2) residing > > >> on a Samsung 850 Pro SSD: > > >>=20 > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 !=3D > > >> bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=3D bp: 0xd9fba319 > > >> handle_workitem_freefile: got error 5 while accessing filesystem > > >> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d= 2a3 > > >> !=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 > > >=20 > > > It indicates a problem. We've seen these 'corruptions' on data in mot= ion at > > > work, but I hacked fsck to report checksum mismatches (it silently co= rrects > > > them today) and we've not seen any mismatch when we unmount and fsck = the > > > filesystem. =20 > > Not sure this helps: But we have seen this also after system panics > > when having soft update journaling enabled. Having soft update journali= ng > > 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. > >=20 > > You can check using tunefs -p devname if soft update journaling is enab= led or > > not. =20 >=20 > 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). ... and journalling as well! In case of the SD, I produced the layout of the NanoBSD image via "dd" incl= uding the /cfg partition. The problem occured even when having overwritten the SD card wit= h a new image. The problem went away once I unmounted /cfg and reformatted via newfs. Afte= r that, I did not see any faults again! I have no explanation for this behaviour except t= he dd didn't overwrite "faulty" areas or the obligate "gpart recover" at the end of the = procedure restored something faulty. The /tmp filesystem I reported in was also from an earlier date - and I did= n't formatted it as I said - I confused the partition in question with another one. The p= artition has been created and formatted months ago under CURRENT. In single user mode, I reformatted the partition again - with journaling an= d softupdates enabled. As with the /cfg partition on NanoBSD with SD card, I didn't reali= se any faults again since then.=20 >=20 >=20 > >=20 > > Best regards > > Michael =20 > > >=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" =20 > >=20 > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" =20 >=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/ZmNi6G2KhPSkwUp9=voe_7f Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWlIFMQAKCRDS528fyFhY lKOVAf9U0wLiMcFmMo6vj+YFoRo8OZVXJTENyPXV1nUxL0Hwz4kQ7D2n3i+OJD9y fgDfS9JDmLDqH/9/61GxVYkG3Z5CAf9f2Bc3g3RDqLCp0bnFtL36Uf2bETCNEDt6 zxpzawAJgjPo3OsIQZaxqLVfJg6P6bh+su0hU8la8m/+I85fl77Y =xzmX -----END PGP SIGNATURE----- --Sig_/ZmNi6G2KhPSkwUp9=voe_7f--