From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: Corruption: --fix-fixable results in all nlink values = 0 Date: Wed, 21 Aug 2002 14:33:36 +0400 Message-ID: <3D636C80.4030605@namesys.com> References: <3D5E9D69.1030109@namesys.com> <20020819092023.B1815@namesys.com> <3D60AF63.6040809@namesys.com> <20020819124649.A2585@namesys.com> <3D60B6E2.7050006@namesys.com> <20020819132252.A4346@namesys.com> <3D60C35E.7000903@namesys.com> <20020819142035.A5741@namesys.com> <1029875053.12387.521.camel@tiny> <20020821100452.A10765@namesys.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Oleg Drokin Cc: Chris Mason , Matthias Andree , reiserfs-list@namesys.com, god@namesys.com, mason Oleg Drokin wrote: >Hello! > >On Tue, Aug 20, 2002 at 04:24:13PM -0400, Chris Mason wrote: > > > >>make sure it was valid, regardless of where you stored it. The problem >>is that if you store it in the tree somehow, you've got a chicken and >>egg problem that you can't read the list until the tree is good and you >>can read the tree without knowing which blocks are bad. >> >> > >With carefully choosen key, it will be in fixed tree position. >But well, if Hans decided it should not be stored in a tree - so be it. > >Bye, > Oleg > > > > It is not that I oppose putting it into the tree with a fixed key for the file holding it, it is that I want us to work on other things instead. Hans