Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 2013 15:46:50 -0400
From:      Michael Powell <nightrecon@hotmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: SU+J Lost files after a power failure
Message-ID:  <l3hhn1$6ga$1@ger.gmane.org>
References:  <525A6831.5070402@gmail.com> <l3gc7e$c91$1@ger.gmane.org> <20131014133953.58f74659@gumby.homeunix.com> <525C1D1C.9050708@gmail.com> <CA+tpaK2Pr2po2cQ1yanQK9+wLp77SYqYHjxiXaU5FfXwHrkGow@mail.gmail.com> <CAFYkXjn-1wTJcQ4a_fyXCvwh9ukt3+djM2qsMeaH1HhVJNvhiA@mail.gmail.com> <525C2554.7080203@pchotshots.com> <CAFYkXjm8y0Br31_pqRZc0sNFbqCNtKHhjeQuiLXkGT2zxSu0GA@mail.gmail.com> <525C2FBC.4080808@cran.org.uk> <CAFYkXj==tiKSAJh3kkCnonsqAaDg_sHYYEUnfLKWLaR-GD-Nzw@mail.gmail.com> <F2D0FD23-884F-48D4-865B-CE793E2B4F39@mac.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Charles Swiger wrote:

[snip]
 
> Yes.  Without journalling, you'd normally perform the full timeconsuming
> fsck
> in the foreground.  With journalling, it should be able to do a journal
> replay to restore the filesystem to an OK state, but sometimes that
> doesn't restore consistency, in which case it usually fires off a
> background fsck rather than the foreground fsck.

In my case the journal replay failed, with an error to that effect. All 
partitions other than / failed to mount and after hitting enter at the 
.../bin/sh prompt performed manual fsck on all of them, which found and 
fixed some stuff. Then shutdown -r and everything came up fine (clean) 
afterwards. Net result was no data loss for me.

[snip]

-Mike





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?l3hhn1$6ga$1>