Date: Tue, 27 Dec 2011 14:48:46 -0800 From: Xin Li <delphij@delphij.net> To: David Thiel <lx@redundancy.redundancy.org> Cc: d@delphij.net, freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves Message-ID: <4EFA4B4E.201@delphij.net> In-Reply-To: <20111227223638.GK45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <CAGMYy3t3Rv006qvBCHr4kdbM86andkr5mRkvaGYw5CETO1XHkg@mail.gmail.com> <20111227223638.GK45484@redundancy.redundancy.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/27/11 14:36, David Thiel wrote: > 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. fsck -p perhaps? IIRC the fsck_ufs(8) would use journal if it's available and up-to-date. Cheers, - -- Xin LI <delphij@delphij.net> https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk76S04ACgkQOfuToMruuMChEACfXyh1Y7IGiATqJdnFKeuIS2vB vJMAn0gCPy98kohAh3LD9ieIASPmksHd =L7lN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFA4B4E.201>