On Fri, Jun 21, 2019 at 1:56 PM Scott Long <sco...@samsco.org> wrote: > > > > > On Jun 21, 2019, at 1:49 PM, Alan Somers <asom...@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 _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
