Re: SU+J systems do not fsck themselves

看板FB_current作者時間14年前 (2011/12/28 07:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串4/16 (看更多)
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. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
文章代碼(AID): #1E-auk0k (FB_current)
討論串 (同標題文章)
文章代碼(AID): #1E-auk0k (FB_current)