Re: r5 hash detected, unable to force r5 hash

[Oleg Drokin <green@namesys.com>]

Hello!

   This is user error.
   Because it is clearly stated that if you want to convert to new hash,
   you need to backup your data, reformat FS with new hash and put all the
   data back.

   User errors are dealt with based on http://namesys.com/support.html
   terms.

Bye,
    Oleg
On Fri, Apr 19, 2002 at 08:57:15PM +0200, Frederick Page wrote:
> G'day everybody,
> 
> I'm using GNU Debian 2.4.13-ac8 with (included) reiserfs 3.6.25, I
> created the partition with "mkreiserfs /dev/sdb1" (defaults) (defaults)
> (defaults) (defaults) (defaults) (defaults) (defaults) (defaults) and
> mounted like this (/etc/fstab):
> 
> /dev/sdb1   /sound    reiserfs defaults   0    1
> 
> Everything worked fine, I have the freedb database with 550,000 small
> files on /sound, performance was much better than ext2. I then read
> about different hashes, umounted /sound, edited fstab and remounted
> it.
> 
> /dev/sdb1   /sound    reiserfs hash=tea   0    1
> 
> Mount was successful, however I only got the root-directories with "no
> such file". Well, just change fstab to "hash=r5", things should be back
> to normal. I then tried to mount /sound, realized, that it was still
> mounted. 
> 
> Now I may have committed a big mistake: I just umounted /sound (although
> fstab was already showing r5, but volume was still mounted with tea).
> 
> Then mounted again (fstab still showing r5) and got:
> 
> REISERFS: Error, r5 hash detected, unable to force r5 hash
> 
> "debugreiserfs /dev/sdb1" says:
> Hash function used to sort names: "tea"
> 
> Since then, I am unable to change the hash, I can mount the partition
> with "hash=detect" or "hash=tea", but then I cannot retrieve any data.
> 
> I researched via Google and the archive of this mailing list, found out
> that the above error is quite old (probably fixed by now). I also
> followed the advice on the main page to use kernel 2.4.18 because of
> bug-fixes, but this did not change anything, I am unable to mount with
> r5 hash.  (ReiserFS is still version 3.6.25 with kernel 2.4.18).
> 
> "reiserfsck --check /dev/sdb1" gives lots and lots of errors and the
> recommendation to rebuild the tree (which I did not do, because I am not
> sure, whether this might do more harm than good in this case).
> 
> I would very much appreciate any help, as I am struggling for my data.
> 
> Thanks for reading all this and kind regards
> 
> Frederick
> 
>