Date: Tue, 11 May 2021 23:14:54 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 255799] ffs crash on ufs file system Message-ID: <bug-255799-3630-2RpXE1hPpL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255799-3630@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255799 Kirk McKusick <mckusick@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mckusick@FreeBSD.org --- Comment #2 from Kirk McKusick <mckusick@FreeBSD.org> --- What were the details on the filesystem in question (df information, and ideally the first 100 lines of dumpfs of the filesystem). Were you running it using soft updates or journalled soft updates? Were there any I/O errors reported for the drive in the system logs. Did you run fsck on it after the crash, and if so what if any errors did it report/fix? If you were running your filesystem with journalled soft updates, please try running a full fsck check on it (fsck -f). A drawback of any journalling filesystem is that it only checks things that it thinks might be wrong. If a disk error occurs, then unexpected data can get corrupted and a journal rollback will not fix it. Only a full check of the filesystem will do so. And as long as it is not fixed, you will keep tripping over the same error/panic until you do fix it. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255799-3630-2RpXE1hPpL>