Date: Fri, 12 Jan 2018 08:51:31 -0700 From: Warner Losh <imp@bsdimp.com> To: Ed Maste <emaste@freebsd.org> Cc: Michael Tuexen <tuexen@freebsd.org>, "O. Hartmann" <ohartmann@walstatt.org>, 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: <CANCZdfpPfoai87SdBPG1EwZF1pgPZ04jZeicRsiZKV3m3iWA9w@mail.gmail.com> In-Reply-To: <CAPyFy2DM-t=DVwftp0RqOjjE9CXZY9=g5=23HO-dYVS%2B%2BMMMTg@mail.gmail.com> References: <20171231004137.4f9ad496@thor.intern.walstatt.dynvpn.de> <CANCZdfoMdgCrAAXadc-G6v1r0wA-qv=Ms_XKYPd7cFqSc5%2B9GQ@mail.gmail.com> <23651B78-E31C-4BDD-BCA3-408B8F907884@freebsd.org> <CAPyFy2DM-t=DVwftp0RqOjjE9CXZY9=g5=23HO-dYVS%2B%2BMMMTg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Fri, Jan 12, 2018 at 8:28 AM, Ed Maste <emaste@freebsd.org> wrote: > On 4 January 2018 at 03:10, Michael Tuexen <tuexen@freebsd.org> wrote: > > > > 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. > > Both of my new co-op students have encountered this as well: after a > panic (unrelated to the filesystem), SU+J fsck recovery runs at boot, > and than many cylinder checksum warnings are emitted by the kernel. > The students used the default installer configuration; it sounds like > we should disable SU+J by default in the installer until this issue is > addressed. > I've posted https://reviews.freebsd.org/D13884 as well to change fsck from silently fixing the cg checksum to one that's whiny about it as well. Warnerhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpPfoai87SdBPG1EwZF1pgPZ04jZeicRsiZKV3m3iWA9w>