slaveunit

Here were my results. There was a newly created lost+found with nothing in it. After remounting everything seems normal again. Thanks Joe L. reiserfsck --rebuild-tree started at Sun Jun 26 23:22:51 2011 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 450959478 blocks marked used Skipping 23115 blocks (super block, journal, bitmaps) 450936363 blocks will be read 0%.. left 406925961, 29242 /sec left 84571607, 24259 /secc left 0, 21907 /secc 3962 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 450936363 Leaves among those 445704 - leaves all contents of which could not be saved and deleted 1 Objectids found 3964 Pass 1 (will try to insert 445703 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 66 /sec Flushing..finished 445703 leaves read 445701 inserted 2 not inserted ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....100% left 0, 0 /sec Flushing..finished Leaves inserted item by item 2 Pass 3 (semantic): ####### Pass 3 ######### ... s - The Pathologists Report Part IV Epidemic/CARCASS CHAPTER 4 MOSH 097.isovpf-10680: The file [392 393] has the wrong block count in the StatData (5031936) - corrected to (832248) Flushing..finished Files found: 3553 Directories found: 411 Broken (of files/symlinks/others): 1 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished13, 39 /sec Pass 4 - finished done 428543, 27 /sec Deleted unreachable items 518 Flushing..finished Syncing..finished ########### reiserfsck finished at Mon Jun 27 11:23:55 2011 ###########

I get the feeling this is going to take quite a long time on a 2tb drive moving at 30MB/sec.

Today I was using MC to move some files around and one certain ones I received and error that stated they cannot be deleted because the filesystem is read only. I looked in the syslog and it kept repeating that one of the blocks was bad on my disk and that I should run FSCK. So I stop samba and unmount the drive then proceed to run the reiserfsck --check /dev/md5 command. Here are my results. Just to be safe I would like to get some opinions if I should proceed or not. This is version 4.6 and I did not save my syslog before rebooting. I know I should have. root@Tower:~# reiserfsck --check /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md5 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sun Jun 26 21:09:29 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. \/ 4 (of 18|/ 27 (of 153\/104 (of 114\block 20114674: The level of the node (33576) is not correct, (1) expected the problem in the internal node occured (20114674), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sun Jun 26 22:43:25 2011 ###########