Date: Fri, 31 Aug 2012 08:44:31 -0700 (PDT) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-current@freebsd.org Subject: Re: UFS journal error on 10.0-CURRENT Message-ID: <1346427871725-5739669.post@n5.nabble.com> In-Reply-To: <CADL2u4joKxG7aZhRT%2Br8cW6ygjzW%2BGKonkHzspswdBYR9HhLQg@mail.gmail.com> References: <CADL2u4j1rJfvx1QnpD3kiJxQ1rb04amOHx__C9fHQJPEAZtNbg@mail.gmail.com> <1346329887307-5739274.post@n5.nabble.com> <alpine.BSF.2.00.1208301942100.1498@s560x.c0c0.intra> <1346359078818-5739408.post@n5.nabble.com> <CADL2u4joKxG7aZhRT%2Br8cW6ygjzW%2BGKonkHzspswdBYR9HhLQg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> That's normally the case, yes, but not here. Are you saying that if using journal, inconsistencies in 'clean' fs are expected? Basically I'm saying that apparently here journal does nothing after enabling it. Usually after really hard power dip, I need to manually fsck as all symptoms of unclean fs are apparent. Maybe disabling; fsck; removing journal file; and reenabling it could fix it too? Yes, I'm afraid of it... -- View this message in context: http://freebsd.1045724.n5.nabble.com/UFS-journal-error-on-10-0-CURRENT-tp5739231p5739669.html Sent from the freebsd-current mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1346427871725-5739669.post>