From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vitaly Fertman <vitaly@namesys.com>
Subject: Re: fsck.reiser4
Date: Thu, 25 Dec 2003 20:00:52 +0300
Message-ID: <200312252000.52880.vitaly@namesys.com>
References: <200312251542.28769.janfengler@web.de>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <reiserfs-list-return-16401-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <200312251542.28769.janfengler@web.de>
Content-Disposition: inline
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: janfengler@web.de, Reiserfs Mailinglist <reiserfs-list@namesys.com>

On Thursday 25 December 2003 17:42, janfengler@web.de wrote:
> Hello,

Hello Jan,

> i have an Problem using fsck.reiser4:
> I've copied my whole system to an newly formatted Reiser4-partition. Just
> after unmounting i ran fsck.reiser4. There where lots of fixable minor
> corruptions so i used fsck.reiser4 again submitting --fix to it. After the
> Run it told me that it has found an corruption correctable using the
> "--fix"-option. Therefore i ran it again, but it seems that fsck.reiser4
> isn't able to correct it. It tells me after every run to run it again with
> the "--fix"-option to correct the problem, wasting my time and doing
> nothing else.

right, the problem can be fixed only by --build-fs but was counted 
as fixable corruption. Will be fixed.

Thank you for the report,
Vitaly Fertman