From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: ReiserFS problems Date: Thu, 07 Aug 2003 17:35:19 +0400 Message-ID: <3F325597.30209@namesys.com> References: <20030806182055.A28562@bitwizard.nl> <20030806164852.GA14719@namesys.com> <20030806192227.B31496@bitwizard.nl> <200308062201.15385.vitaly@namesys.com> <20030806201405.A1357@bitwizard.nl> <20030806202252.A1940@bitwizard.nl> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <20030806202252.A1940@bitwizard.nl> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Rogier Wolff Cc: Vitaly Fertman , Oleg Drokin , reiserfs-list@namesys.com, copy@harddisk-recovery.nl Rogier Wolff wrote: >On Wed, Aug 06, 2003 at 08:14:05PM +0200, Rogier Wolff wrote: > > >>You can verify on >> >> http://www.bitwizard.nl/io_throughput.gif >> >>that (almost) no data was written throughout the first pass. >> >> > >It seems to have dropped into a different pass again: throughput has >dropped to just over 300k per second. > >Should I feel comfortable if it's finding formatting errors all over >the place?: > > entry [x y] "ZZZ" in directory [a b] is not formatted properly -- fixed. > >(usually x == 2, a,b == 1,2 .) > >Tip: > >Only list the file/directory that's being worked upon when explicitly >requested. When not explicitly requested, set an alarm handler to >print it every second (or so). Lots of time is now spent in writing to >the screen. (It's consumed over an hour of CPU time by now...) > > Roger. > > > > good point. Vitaly, do this unless you have a reason not to. -- Hans