Date: Tue, 27 Dec 2011 14:37:02 -0759 From: David Thiel <lx@redundancy.redundancy.org> To: Xin LI <delphij@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves Message-ID: <20111227223638.GK45484@redundancy.redundancy.org> In-Reply-To: <CAGMYy3t3Rv006qvBCHr4kdbM86andkr5mRkvaGYw5CETO1XHkg@mail.gmail.com> References: <20111227215330.GI45484@redundancy.redundancy.org> <CAGMYy3t3Rv006qvBCHr4kdbM86andkr5mRkvaGYw5CETO1XHkg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 27, 2011 at 02:29:03PM -0800, Xin LI wrote: > I'm not sure if your experiments are right here, the second log shows > you're running it read-only, which is likely caused by running it on > live file system. Yes, this most recent instance is me running it on a live FS, because I'm using that machine to type this right now. :) However, I've had the issues fixed in single-user on other systems and had the problems go away. At least for a bit. > - use journalled fsck; > - use normal fsck to check if the journalled fsck did the right thing. When you say "use journalled fsck", what's the proper way to initiate that? I don't see any journal-related options in the man page.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111227223638.GK45484>