Date: Sun, 08 May 2016 16:22:56 +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-qJFfuZrI60@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208691-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-208691-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=3D208691 --- Comment #6 from Kirk McKusick <mckusick@FreeBSD.org> --- You suggest ``An alternative to prevent the observed behaviour, of rebooting continually, would be to always fully fsck the filesystem when it is dirty, rather than the current fsck -p behaviour of replaying the journal and appl= ying simpler checks.'' To get this behavior, turn off journalling using the command: tunefs -j disable /filesystem/to/disable When the system finds a clean filesystem at boot, it skips fsck. When the system finds a dirty filesystem at boot and no journal, it runs a full fsck. You note ``I'm not sure a new "filesystem panic flag" would help, as there's not a lot of difference between the state the FS can be left in after to a kernel panic and when it stops due to a power failure.'' When a panic occurs, the filesystem code never gets another chance to run, = thus there is no way for it to set a `filesystem panic'ed flag'. The only indica= tion of something unexpected having happened is the absence of a `filesystem cle= anly unmounted flag'. --=20 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-208691-3630-qJFfuZrI60>