Date: Mon, 11 Apr 2016 22:36:32 +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-q7m4tZOlg7@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 Kirk McKusick <mckusick@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mckusick@FreeBSD.org --- Comment #1 from Kirk McKusick <mckusick@FreeBSD.org> --- This is a known problem with journaled soft updates. It only fixes things t= hat are in its log. Most disks are run with write cache enabled which means that they lie about completing I/O operations. Specifically they report that an = I/O has been made to stable store when in fact it is only in the RAM-cache on t= he disk. If power to the disk is lost before the cache is flushed, the write is lost, but journaled soft updates believes it to have been done so does not check for the error. Thus it marks the disk clean when in fact it is not cl= ean. To resolve this problem, you must bring the machine up single user and run a full fsck on it using ``fsck -f -y /filesystem_in_question''. This will find the hidden problem and correct it. --=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-q7m4tZOlg7>