Date: Wed, 19 Feb 2014 13:54:37 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Warren Block <wblock@wonkity.com>, David Demelier <demelier.david@gmail.com> Subject: Re: FreeBSD FFS SU+J is not stable Message-ID: <201402191354.37749.jhb@freebsd.org> In-Reply-To: <alpine.BSF.2.00.1402190950420.58832@wonkity.com> References: <CAO%2BPfDebTbZXOJp00rZYZP3BvL3CHF2AH4JwNZpjauOKoa5rHg@mail.gmail.com> <alpine.BSF.2.00.1402190950420.58832@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, February 19, 2014 11:53:13 am Warren Block wrote: > On Wed, 19 Feb 2014, David Demelier wrote: > > > Running 10.0-RELEASE, it is the second time I have a power failure and > > bad shutdown. It's also the second time I get a fsck failure. This > > time fsck has even segfault'ed. > > > > I think I will switch to ZFS. > > > > This is the log of the next boot up : http://imgur.com/rRpREKP > > > > Is it possible to automatically run fsck manually after this kind of failures? > > Yes, but I would suggest turning off SUJ instead. Soft updates alone > have been reliable for me. SUJ, not really. I still have SUJ enabled on my laptop, but I routinely get segfaults in fsck when rebooting after a panic. Also, I now always run a full fsck after the journal fsck (which does sort of defeat the point of SUJ) and it generally finds missing blocks that are free but marked in use. I've reported details about the fsck segfaults in the past to no avail. :( -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402191354.37749.jhb>