> Just to make sure I understand, you had the exact same errors before
> running fsck? Same files could not be deleted?
Correct.
> > I think this is a problem with the reiserfs code in the kernel. I never
> > ran reiserfsck before this problem surfaced. The problem arose in the
> > netscape cache directory with lots of small files. Guess the tail handling
> > is not that stable yet?
>
> I wish I could blame it on the tail code ;-) None of the bugs fixed there
> would have caused this, and they should be completely unrelated. I'll try
> some tests in oom situations to try and reproduce. It could also be caused
> by hashing errors. If you formatted with r5 hash, was the partition ever
> incorrectly detected as tea hash?
No idea. I never got that deep into reiser.
> > How do I get rid of the /a/yy directory now?
>
> With fsck. I'll grab the latest today and make sure it can fix this bug.
> Until then, mv /a/yy /a/yy.broken and mkdir /a/yy.
/a/yy is already a "broken" dir moved out of the way.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/