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: Mon, 19 Aug 2002 14:27:59 +0400 Message-ID: <3D60C82F.1080403@namesys.com> References: <200208161205.00550.vitaly@namesys.com> <200208170254.48383.degerrit@web.de> <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> 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: Matthias Andree , reiserfs-list@namesys.com, god@namesys.com, mason Oleg Drokin wrote: >Hello! > >On Mon, Aug 19, 2002 at 02:07:26PM +0400, Hans Reiser wrote: > > > >>>He suggests that user should specify list of bad blocks each time user runs >>>reiserfsck. >>> >>> >>This sounds reasonable. You can probably even have a default location >> >> > >Not for me. > > > >>to check for the list somewhere in /etc if you want. Remind the user >> >> > >File can get corrupted too. > > > > >>that you are using it everytime you find it though, that way if a >>different sysadmin is running fsck, they can know why not all the blocks >>they expect to be there are accessible. >> >> > >Having some config files for this purpose is not good. >What if I have booted from rescue disk? > >Bye, > Oleg > > > > That is why it is only the DEFAULT location, and (slight improvement here) the user is prompted about whether to use it.