Date: Mon, 25 Feb 2019 23:45:26 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 223491] fsck_ufs: Directory XXXX name not found Message-ID: <bug-223491-3630-pMj2JStRDI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223491-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-223491-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223491 Kirk McKusick <mckusick@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mckusick@FreeBSD.org Status|New |Closed Resolution|--- |Not A Bug --- Comment #8 from Kirk McKusick <mckusick@FreeBSD.org> --- This bug falls into the class of bugs that occur when using journalling. Specifically, the journal only tracks inconsistencies that can occur based on the order of the write completions to the disk. If the disk lies about write completions, then the disk will be inconsistent in ways that the journal does not know. Recovery using journalling is quick, because it only checks the things that it knows may be wrong. If other errors have occurred, the journal will not fix them. Running fsck -f ignores the journal and does a full consistency check of the disk so will find and fix the errors about which the journal is unaware. When running on lying disks, you should NOT use journalling. Rather run with just soft updates. After a crash it will take longer to come back up, but all of the problems will be found and fixed. You can disable journalling using the command `tunefs -j disable'. When creating new filesystems, use `newfs -U ...' instead of `newfs -j ...'. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223491-3630-pMj2JStRDI>