Re: problem with corrupted filesystem

[Marcus Becker <Becker_Marcus1@web.de>]

kk, thanks for the answer

I just read that other mail from Jonas and thought I give it a shot.
Nothing changed on the filesystem.
If you need more information, let me know.

Marcus

-----Ursprüngliche Nachricht-----
Von: Edward Shishkin <edward.shishkin@gmail.com>
Gesendet: Mar 30, 2010 11:07:32 PM
An: Marcus Becker 
Betreff: Re: problem with corrupted filesystem

>Marcus Becker wrote:
>> Hi,
>>
>> I tried using hash=tea as mount option with the same result.
>>   
>
>I don't think that reiser4 supports such mount option
>
>> Is this something I can change on an already formatted partition?
>>   
>
>What do you want to change? IMHO the type of hash can be assigned only
>in mkfs time. There was an interface to change it on-line per-directory (via
>so-called pseudo-files), but this is still deprecated and is not used.
>
>> Where can I check, which hash is used?
>
>In the plugin table of (root) directory of debugfs.reiser4 -t output.
>Attributes of other objects are inherited through the semantic tree
>by default and, hence, are not shown.
>
>In your case (that you have sent me) we have the following:
>
>NODE (715370) LEVEL=1 ITEMS=22 SPACE=0 MKFS ID=0x7c4de18e FLUSH=0x0
>#0  SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0
>[...]
>permission : id = 0
>formatting : id = 2 (smart)
>hash : id = 1 (r5_hash) <<<<<<<<<<<<<<<
>fibration : id = 2 (ext_1_fibre)
>statdata : id = 0 (stat40)
>diritem : id = 2 (cde40)
>crypto : id = 0
>digest : id = 0
>compress : id = 0 (lzo1)
>compressMode : id = 4 (conv)
>cluster : id = 0 (64K)
>create : id = 0 (reg40)
>
>Edward.
>
>>  /proc/mounts doesn't list the option.
>>
>> Thanks,
>>
>> Marcus
>>
>
___________________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
--
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