Apologize me about my ignorance, but with this procedure can be any data
lost?.. I don't have any other 260GB to make a backup. If this procedure is
safe, I will do it immediatly and send you the reports.
Thanks a lot
> Hi,
>
> you have to rebuild your partition. Usually we recommend to dd the
parttion
> somewhere, but I do not think you have another 260G, so I would recommend
> to run :
> touch somefile-on-non-reiserfs
> 3.x.0j/debugreiserfs -p .bitmap /dev/xxx | 3.x.0j/unpack
somefile-on-non-reiserfs
> and
> 3.x.0k-pre9/reiserfsck --rebuild-tree -l logfile somefile-on-non-reiserfs
> If it works OK, run
> rm somefile-on-non-reiserfs
> 3.x.0k-pre9/reiserfsck --rebuild-tree -l logfile /dev/xxx
>
> If not, send me the logfile and describe details.
> NOTE: the file somefile-on-non-reiserfs contains just metadata of files,
> and will take much less space.
>
> > Ok, sorry for not include a complete information, I am running in a RH
7.1
> > distribution and using an 2.4.6 kernel with no patches or fixes... I
have
> > just downloaded the reiserfsprogs 3.x.0k-pre9 and cheked the partition..
> > The reiserfsck log reported that:
> >
> > bad_leaf: block 45031 has invalid item 4: 67 160 0x1 DIR (3), len 1672,
> > location 888 entry count 66, fsck need 0, format old
> > bad_leaf: block 562713 has invalid item 3: 57770 57716 0x1 DIR (3), len
> > 1608, location 2304 entry count 43, fsck need 0, format old
> > check_semantic_pass: hash mismatch detected (cic-2dm1.r24-missing)
> > check_semantic_pass: hash mismatch detected (ih.foopre-tmp)
> >
> >
> > umm, does reiserfsck detect and mark bad blocks in hds or fix them?
> >
> >
> > Thanks again
> --
>
> Thanks,
> Vitaly Fertman
>
