----While looking at disk 1, we ran the File System Check and it showed errors (see below).

----We then ran

Cd

Samba stop

Unmount /dev/md1

reiserfsck –fix-fixable /dev/md1    Yes

mount /dev/md1 /mnt/disk1

samba start

----Once this was done we re-ran the File System Check and again received the errors, with the parameter for –rebuild-tree.

----Under the wiki it talks about the evils of the –rebuild—tree

----WHAT ACTION do we need to take!?

 

 

 

Comparing bitmaps..Fatal corruptions were found, Semantic pass skipped

1 found corruptions can be fixed only when running with --rebuild-tree

###########

reiserfsck finished at Wed Oct 20 00:34:05 2010

###########

bad_indirect_item: block 74890760: The item (6 21498 0xbb2d001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (74939626), which is in tree already

bad_indirect_item: block 184032838: The item (51 2803 0x178205001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (185593105), which is in tree already

bad_indirect_item: block 126926559: The item (3973 3975 0x28d7cf001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (129639667), which is in tree already

bad_indirect_item: block 55187707: The item (7196 7511 0x409cb001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (98) to the block (55481379), which is in tree already

bad_indirect_item: block 28903070: The item (118619 118850 0x6001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (28903433), which is in tree already

bad_indirect_item: block 147731013: The item (158265 158310 0x2815de001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (866) to the block (173922248), which is in tree already

bad_indirect_item: block 51442051: The item (158271 568367 0x151283001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (53110752), which is in tree already

bad_indirect_item: block 35292740: The item (294988 294993 0x1875e6001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (36962376), which is in tree already

bad_indirect_item: block 65675215: The item (311838 311850 0x3bb1001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (65690802), which is in tree already

bad_indirect_item: block 55030661: The item (431679 431684 0x2c796b001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (59943921), which is in tree already

bad_indirect_item: block 77758620: The item (457049 457498 0xa92001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (77775642), which is in tree already

bad_indirect_item: block 54586131: The item (568383 568386 0x3ad976001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (354) to the block (68190114), which is in tree already

bad_leaf: block 84569681, items 59 and 60: The wrong order of items: [661420 663734 0x0 SD (0)], [661416 663734 0x1 IND (1)]

vpf-10640: The on-disk and the correct bitmaps differs.

 

 

You must now use the rebuild-tree option. 

 

The warning in the wiki is probably worded too strongly.  It should probably be changed.  if a prior "check" says you need to rebuild the file-system tree, you need to do that next.

 

Joe L.