Re: File Corruption

[Oleg Drokin <green@namesys.com>]

Hello!

On Tue, Oct 01, 2002 at 09:07:34PM -0700, jeff leads wrote:

> Hi!  Below is the abbreviated version of my output
> from --check.  Is it safe to run --fix-fixable?

Hm. No signs of that bad corruption your kernel was reporting.

>  What do the bad nlink numbers mean?  Should I be

These are "lost" files most probably. Bad nlink means that file have
nlink count of zero.

> concerned about the dirty buffers?

Hm. Can you get resiserfsprogs 3.6.4-pre3 from our ftp site
(ftp://ftp.namesys.com/pub/reiserfsprogs/pre) and give it a try,
if this "dirty buffers" message persists, please take metadata snapshot for us
( debugreiserfs -p /dev/your_device | gzip -9c >metadata.gz ).
Also resiserfsprogs 3.6.4-pre3 would tell you that you need
rebuild tree most probably (because now nlink number correction is only done
on rebuild-tree stage), so you would need to do rebuild-tree.

Bye,
    Oleg