From mboxrd@z Thu Jan 1 00:00:00 1970 From: mjt@nysv.org Markus =?unknown-8bit?q?T=F6rnqvist?= Subject: Re: fsck 0.5.5 time Date: Fri, 18 Jun 2004 15:29:01 +0300 Message-ID: <20040618122901.GI4990@nysv.org> References: <20040618110112.GG4990@nysv.org> <40D2D82B.3090301@namesys.com> <200406181620.25609.vitaly@namesys.com> Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: <200406181620.25609.vitaly@namesys.com> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Vitaly Fertman Cc: "Vladimir V. Saveliev" , reiserfs-list@namesys.com On Fri, Jun 18, 2004 at 04:20:25PM +0400, Vitaly Fertman wrote: >> > How long is the expected time for fsck to run? >depends on the speed of your hardware, kind of corruptions, >fsck options, many things. Yeah, I was just hoping for some rough estimate of a clean filesystem with a some benchmark setup :) Well, it's not that critical. >> > Are there any risks in using the /home/ read-write without the stat data >> > extensions, or whatever --fix fixes? >should be ok, if you are talking about the plugin set that is added into >the root. Well, I guess I am :) I couldn't remember exactly what the new addition that wanted --fix was, but I thought I remembered it was statdata extensions. >yes, you are right, there will be some progress on semtanic pass also, >it has not been implemented yet. Hooray! I owe you a beer :) -- mjt