On Mon, 06 Aug 2001, Rafael Herrera wrote:
> bad_directory_item: block 559823: item 203453 203647 0x1 DIR, len 314, entry count
>12, fsck need 0, format old has entry "." with wrong deh_state 147174
> bad_directory_item: block 559823: item 203453 203647 0x1 DIR, len 314, entry count
>12, fsck need 0, format old has entry ".." with wrong deh_state 147406
> bad_directory_item: block 778847: item 203798 203799 0x1 DIR, len 171, entry count
>7, fsck need 0, format old has entry "." with wrong deh_state 147016
> bad_directory_item: block 778847: item 203798 203799 0x1 DIR, len 171, entry count
>7, fsck need 0, format old has entry ".." with wrong deh_state 147406
> bad_directory_item: block 639932: item 204129 204166 0x1 DIR, len 35, entry count 2,
>fsck need 0, format old has entry "." with wrong deh_state 145706
> bad_directory_item: block 639932: item 204129 204166 0x1 DIR, len 35, entry count 2,
>fsck need 0, format old has entry ".." with wrong deh_state 147424
This warning is result of a harmless bug in kernel 2.2 reiserfs. it does not
affect data consistency.
> Comparing bitmaps..free block count 54701 mismatches with a correct one 54733.
> on-disk bitmap does not match to the correct one. 10 bytes differ
A disc space leak. another bug in kernel 2.2 reiserfs that occures on hard
crashes.
> Checking Semantic tree...check_semantic_pass: hash mismatch detected (M-H3&^HM-
>M-jM-^D@^P)
> check_semantic_pass: hash mismatch detected (M-^Hs4^HM-
> M-^E@^P)
ugh, this looks rather bad.
Dirk
