Re: i/o error (lost+found) with reiser4

[Alex Zarochentsev <zam@namesys.com>]

On Mon, Feb 23, 2004 at 06:20:03PM +0300, Alex Zarochentcev wrote:
> On Sun, Feb 22, 2004 at 11:38:23PM +0100, Henning Westerholt wrote:
> > Hello all,
> > 
> > after the regular stat data error, i try to fix the fs as usual. Today the 
> > fsck program complains the first time about a fatal corruption. I attached 
> > the output from the first fsck run.

Can you tell more about workload which caused the corruption?  Also, we like
to know reiser4 verion, kernel and hardware configuration.

> > 
> > I run fsck with option "build-fs" as recommended, and it seems to fix the 
> > error. But now a "ls" in the root of the reiser4 partiton complains about a 
> > input/ output error on the directory "lost+found". 
> > Output from the system log:
> > 
> > +++++++++
> > reiser4[ls(14750)]: check_open_format40 
> > (fs/reiser4/plugin/disk_format/disk_format40.c:551)[vpf-1360]:
> > WARNING: The object with the oid 3441763 greater then the max used oid 3441762 
> > found.

If there was no fs activity (file creation/deletion) after "build-sb",
you can erase blocks ##19, 20 on the fs:

backup:
dd if=/dev/hdd8 skip=19 bs=4096 count=2 of=hdd8.19-20x4k.dat

erase:
dd if=/dev/zero of=/dev/hdd8 seek=19 bs=4096 count=2 conv=notrunc

> > reiser4[ls(14831)]: check_open_format40 
> > [...the same with stat, bash...]
> > +++++++++
> > 
> > Error messages from ls, stat..:
> > 
> > +++++++++
> > # ls /var/tmp/
> > ls: /var/tmp/lost+found: Input/output error  
> > ccache  distfiles  emerge-webrsync  kdecache-party  portage  portage-pkg  sync 
> > 
> > # stat /var/tmp/lost+found
> > stat: cannot stat `/var/tmp/lost+found': Input/output error
> > 
> > # cd /var/tmp/lost+found
> > -bash: cd: /var/tmp/lost+found: Input/output error
> > 
> > #fsck.reiser4 /dev/hdd8 
> > ...
> > No corruption found.
> > +++++++++
> > 
> > Should i rebuild the partition? Is this a know problem?
> 
> This is not known but I have an idea why it happened.  I will discuss it with
> our fsck maintainer and then we tell you how to fix the corruption. 
> 
> Thanks for the report. 
> 
> > Best regards,
> > 
> > Henning
> 
> -- 
> Alex.

-- 
Alex.