Date: Tue, 12 Apr 2016 19:19:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 208691] "panic: ffs_valloc: dup alloc" as soon as UFS root partition is mounted Message-ID: <bug-208691-3630-MYyQOpWIv3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208691-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=208691 --- Comment #3 from Kirk McKusick <mckusick@FreeBSD.org> --- To your question of recovering when you have a corrupted root filesystem, that is not a problem because the kernel always comes up with the root filesystem read-only. The panics that you can get will only happen when attempting to write the filesystem. So if you are single-user, you will have the opportunity to fix the filesystem while it is mounted read-only. It only switches to read-write as it exits single-user and goes to multi-user. The long-term fix is to note in the superblock when the filesystem has panic'ed and to force a full fsck when finding this flag set. This is part of a bigger project that reduces the number of panics in the filesystem that should be coming in over the next year. As a general rule, you should run with write cache disabled if you want full recoverability after a crash. -- 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-208691-3630-MYyQOpWIv3>