Date: Sun, 7 Jan 2018 12:31:34 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: Michael Tuexen <tuexen@freebsd.org>, Warner Losh <imp@bsdimp.com>, FreeBSD CURRENT <freebsd-current@freebsd.org> 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> <CANCZdfoMdgCrAAXadc-G6v1r0wA-qv=Ms_XKYPd7cFqSc5%2B9GQ@mail.gmail.com> <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> <20180104121447.4d9109ed@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--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" <ohartmann@walstatt.org> schrieb: > On Thu, 4 Jan 2018 09:10:37 +0100 > Michael Tuexen <tuexen@freebsd.org> wrote: >=20 > > > On 31. Dec 2017, at 02:45, Warner Losh <imp@bsdimp.com> wrote: > > >=20 > > > On Sat, Dec 30, 2017 at 4:41 PM, O. Hartmann <ohartmann@walstatt.org>= 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180107123201.19ea0fde>