Reiser4 on 2.6.31.4 freezes process accessing file, fsck 1.0.7 finds no inconsistency

Reiser4 on 2.6.31.4 freezes process accessing file, fsck 1.0.7 finds no inconsistency

[Konstantin]

Hi!

I am running reiser4 for a few years now without problems. Yesterday I
had an undeletable directory which ls -a reported empty but rmdir
claimed not to be empty. There were no kernel messages about it. After
fsck-ing I had to run fsck.reiser4 --build-fs (reiser4progs 1.0.7) which
finished but printed an error at the very end like "application error"
(sorry, I didn't wrote it down). A second run of fsck.reiser4 told me to
fix some remaining corruptions using --fix. This worked without error
messages and a following fsck told me everything is OK.

But then accessing a file froze the process, consuming 100% CPU. I tried
cat and cp with same result. The processes could not be terminated nor
killed. Still no kernel messages. Only rebooting helped here and a
following fsck showed no corruptions. The file could be renamed and
deleted which kind of solved the problem. I haven't found (yet) another
file like this.

Before deleting the bad file I did a debugfs.reiser4 -P to store the
metadata so if anyone is interested in debugging this bug contact me to
give you the file (34MB bz2).

Konstantin

Re: Reiser4 on 2.6.31.4 freezes process accessing file, fsck 1.0.7 finds no inconsistency

[Edward Shishkin]

Konstantin wrote:
> Hi!
>
> I am running reiser4 for a few years now without problems. Yesterday I
> had an undeletable directory which ls -a reported empty but rmdir
> claimed not to be empty. There were no kernel messages about it. After
> fsck-ing I had to run fsck.reiser4 --build-fs (reiser4progs 1.0.7) which
> finished but printed an error at the very end like "application error"
>   

Maybe "Operational error occurred while fscking"?
If so, then you have encountered a bug in fsck.

> (sorry, I didn't wrote it down). A second run of fsck.reiser4 told me to
> fix some remaining corruptions using --fix. This worked without error
> messages and a following fsck told me everything is OK.
>
> But then accessing a file froze the process, consuming 100% CPU. I tried
> cat and cp with same result. The processes could not be terminated nor
> killed. Still no kernel messages. Only rebooting helped here and a
> following fsck showed no corruptions. The file could be renamed and
> deleted which kind of solved the problem. I haven't found (yet) another
> file like this.
>
> Before deleting the bad file I did a debugfs.reiser4 -P to store the
> metadata so if anyone is interested in debugging this bug contact me to
> give you the file (34MB bz2).
>   

Yes, please,
could you provide the metadata for download and the name
of problem file?
Actually, it would be better to have metadata right after the
first fsck complaint about operational error, but anyway,
this is better then nothing..

Thanks,
Edward.

> Konstantin
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>