fsck.reiser4 problem (was: reiser4 corruption problem)

[Michael Weissenbacher <webmaster@dermichi.com>]

> i've already had the exact same problems before, i mean errors like:
> FSCK: Directory [109e8:416c7400000000:109ee] (dir40), node [216782], 
> item [1],
> unit [22]: entry has wrong offset
> [109ee:0(NAME):142657765726275:6e6746fc72416e77:135160352fe624]. Should be
> [109ee:0(NAME):142657765726275:6e6746fc72416e77:13514d8cfe19f4].
> while doing random other things on reiser4 partitions and fsck'ing 
> afterwards. using --build-fs created lots of files under lost+found and 
> i started over. i will leave the fs this time, maybe i can try some 
> things to find the cause of the problem.
i've investigated this problem further the last days and came to the 
following conclusions:
- 2.6.9-rc1-mm1 has a bug that affects all filesystems (pointed out 
earlier today). so don't use if you love your data ;)
- reiser4 is stable for me on 2.6.8.1-mm4 (i compared the directories 
with diff and there were no differences)
- the problem with fsck.reiser4 mentioned above persists. it does not 
like some file names on my partition and then thinks that there are 
fatal corruptions. using "fsck.reiser4 --build-fs" actually destroys 
some data then by moving some correct files to lost+found. the filenames 
fsck does not like all contain german umlauts. but otoh there are 
filenames with umlauts that are ok!

here are some filenames that fail:
BewerbungFürAnwaltsbüro.doc
Graphik01Markenidentität.sxd
SkriptumzumSeminarFühren.doc
WieTeamseffizientwerdenkönnen.doc

but otoh these work:
WerbeKärntnerBallonwerbung.sxw
Vo 08 - 29. März 2001.pdf
TschöranKirche.jpg
VölkermarktKircheGross.jpg

i know that it's never a good idea to use such characters in a file 
name, but tell this to the users ... hopeless!
as i already mentioned earlier, this is with reiserfsprogs-1.0.1

what i learned: don't trust fsck.reiser4 if it says there is corruption 
(yes i know, it could have read README before... sigh)

Michael