Date: Fri, 21 Jun 2019 14:09:38 -0600 From: Alan Somers <asomers@freebsd.org> To: Scott Long <scottl@samsco.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Reducing UFS corruption from unclean shutdowns? Message-ID: <CAOtMX2jXiaOWpVdEg3_nBYinJWd=iwN_38hQ4eMOocgs8dMWhQ@mail.gmail.com> In-Reply-To: <C3016BDF-4B51-4A59-94F2-CCBD0DC4562E@samsco.org> References: <CAOtMX2jPut4ve-Tr7DyikxXqnmqycyjEUpNmAiwUSXbQrK3iCA@mail.gmail.com> <C3016BDF-4B51-4A59-94F2-CCBD0DC4562E@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 21, 2019 at 1:56 PM Scott Long <scottl@samsco.org> wrote: > > > > > On Jun 21, 2019, at 1:49 PM, Alan Somers <asomers@freebsd.org> wrote: > > > > I panic my development VM regularly. Each time, I need to fsck the > > file system. Even if I had run sync(8) just before the panic, I > > frequently find corruption. What should I change to make sync(8) > > work, or at least to make corruption rare? It looks like my root file > > system is using soft-updates+journal. Should I disable those? > > > > What corruption do you regularly see? > > Scott fsck reports various types of errors, all repairable, like "INODE CHECK-HASH FAILED", "FREE BLK COUNT(S) WRONG IN SUPERBLK", "SUMMARY INFORMATION BAD", "BLK(S) MISSING IN BIT MAPS", and "UNREF FILE". If I don't run fsck, then I get errors when I try to access files. Like "inode XXX: check-hash failed" and "such and such is marked as an executable file but could not be run by the operating system". -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jXiaOWpVdEg3_nBYinJWd=iwN_38hQ4eMOocgs8dMWhQ>