August 23, 201213 yr Author I haven't been able to get to my system since the NOCORRECT parity check, but when I do, I want to tackle this incorrectly reported free space issue. Assuming all went well with the parity check, what should be my next step? Should a file system check on the drive fix the wrong free size reported problem?
August 23, 201213 yr I'd try a file system check. Was the old disk5 the same size as the replacement? If no, then you may have to run commands to expand the file system. Good to hear it seems to have worked though.
August 23, 201213 yr Author I'd try a file system check. Was the old disk5 the same size as the replacement? If no, then you may have to run commands to expand the file system. Good to hear it seems to have worked though. Yep, same size drives. Actually same exact drives, 2TB WD Blacks. Heading home now and will run a file system check first and report back.
August 27, 201213 yr Author Wow! What a learning experience. Time to close this one out. Got home and ran a file system check, and sure enough, it requested that I run a --rebuild-tree. I did this, but about halfway in, started getting a good bit of read errors. I suspected a cable problem, not a problem with the drive, but rebuilding the tree was getting to a failing point, so I stopped it knowing that this could be a devastating decision. After re-seating cables, etc, I proceeded to pre-clear the replacement drive for good measure, and for extra good measure, I pre-cleared it again. I then added the drive into the disk5 spot, reset the config, invalidated slot 5, and started the rebuild....again. Once the rebuild started, I noticed the drive was shown as "unformatted" and I had a message in the syslog concerning not being able to mount the drive due to a bad superblock (I figured this was due to me terminating the rebuild-tree command). Regardless, the rebuild of the drive was successful, so I knew it was time to tackle the file system issues. A 'reiserfsck --check' produced a 'Bad root block 0' message: 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 Aug 26 12:44:17 2012 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted Combining this with the message in the syslog about the bad superblock, I figured I needed to rebuild the superblock, then scan and rebuild the tree. Here is the result: root@Tower:~# reiserfsck --rebuild-sb /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 check superblock and rebuild it if needed Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Did you use resizer(y/n)[n]: n rebuild-sb: wrong block count occured (488378638), fixed (488378624) rebuild-sb: wrong free block count occured (488378638), zeroed rebuild-sb: wrong tree height occured (65535), zeroed Reiserfs super block in block 16 on 0x905 of format 3.6 with standard journal Count of blocks on the device: 488378624 Number of bitmaps: 14905 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is clean Tree height: 0 Hash function used to sort names: "r5" Objectid map size 8, max 972 Journal parameters: Device [0x0] Magic [0x6806df07] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x3: FATAL corruptions exist. some corruptions exist. sb_version: 2 inode generation number: 141383 UUID: 3915e40c-fac1-493c-873c-745110598104 LABEL: Set flags in SB: ATTRIBUTES CLEAN Mount count: 27 Maximum mount count: 30 Last fsck run: Mon Dec 19 18:36:29 2011 Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check. The suggested --check still produced the 'Bad root block 0' error, so at this point, it was time to rebuild the tree and not wanting to leave anything in question, went with a --scan-whole-partition as well (I think this is primarily for recovering deleted data, but at this point, figured anything would be good to get out of this). root@Tower:~# reiserfsck --scan-whole-partition --rebuild-tree /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ** 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 rebuild the filesystem (/dev/md5) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Fixed. ########### reiserfsck --rebuild-tree started at Sun Aug 26 13:32:35 2012 ########### Pass 0: ####### Pass 0 ####### The whole partition (488378624 blocks) is to be scanned Skipping 23115 blocks (super block, journal, bitmaps) 488355509 blocks will be read 0%..block 68291055: The number of items (65047) is incorrect, should be (1) - corrected block 68291055: The free space (58943) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 68291055, item (0): Unknown item type found [2147421952 4043308799 0xfffff0108000000 (13)] - deleted block 124369524: The number of items (29440) is incorrect, should be (1) - corrected block 124369524: The free space (63743) is incorrect, should be (976) - corrected pass0: vpf-10110: block 124369524, item (0): Unknown item type found [1828717057 201389567 0x2000701bd00feff (5)] - deleted block 133173034: The number of items (645) is incorrect, should be (1) - corrected block 133173034: The free space (264) is incorrect, should be (3537) - corrected pass0: vpf-10110: block 133173034, item (0): Unknown item type found [151060991 50496768 0x8c000101 (15)] - deleted block 361671850: The number of items (1) is incorrect, should be (0) - corrected block 361671850: The free space (2) is incorrect, should be (4072) - corrected block 362288797: The number of items (5) is incorrect, should be (0) - corrected block 362288797: The free space (4) is incorrect, should be (4072) - corrected block 363026220: The number of items (1) is incorrect, should be (0) - corrected block 363026220: The free space (2) is incorrect, should be (4072) - corrected block 364672792: The number of items (11) is incorrect, should be (0) - corrected block 364672792: The free space (65247) is incorrect, should be (4072) - corrected block 366030089: The number of items (2) is incorrect, should be (0) - corrected block 366030089: The free space (1) is incorrect, should be (4072) - corrected left 0, 28080 /sec 8856 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 488355509 Leaves among those 483564 - corrected leaves 1 - leaves all contents of which could not be saved and deleted 9 pointers in indirect items to wrong area 14 (zeroed) Objectids found 8866 Pass 1 (will try to insert 483555 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 73 /sec Flushing..finished 483555 leaves read 478273 inserted 5282 not inserted non-unique pointers in indirect items (zeroed) 2531 ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....vpf-10260: The file we are inserting the new item (8711 8718 0x71298001 IND (1), len 488, location 3608 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped 100% left 0, 11 /sec Flushing..finished Leaves inserted item by item 5282 Pass 3 (semantic): ####### Pass 3 ######### /Complete/Happy Birthday.movvpf-10680: The file [4 770] has the wrong block count in the StatData (238968) - corrected to (236816) /Movies/Bluray/Donnie.Darko.(2001)/BDMV/STREAM/00097.m2tsvpf-10680: The file [122 2579] has the wrong block count in the StatData (38567040) - corrected to (31162272) /Movies/Bluray/Burn.After.Reading.(2008)/Burn.After.Reading.mkvvpf-10680: The file [35 39] has the wrong block count in the StatData (51111744) - corrected to (51111632) Flushing..finished Files found: 7927 Directories found: 876 Broken (of files/symlinks/others): 1 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: /758_8711rebuild_semantic_pass: The entry [8711 8744] ("CONSTANTINE.meta") in directory [758 8711] points to nowhere - is removed rebuild_semantic_pass: The entry [8711 8754] ("Subtitles_12_English_exp.sup") in directory [758 8711] points to nowhere - is removed rebuild_semantic_pass: The entry [8711 8719] ("Chapters_2.txt") in directory [758 8711] points to nowhere - is removed /Audio_5_English.W64vpf-10670: The file [8711 8716] has the wrong size in the StatData (0) - corrected to (6261678080) vpf-10680: The file [8711 8716] has the wrong block count in the StatData (1039462) - corrected to (12229840) /Audio_5_English.WAVvpf-10670: The file [8711 8717] has the wrong size in the StatData (0) - corrected to (6257692672) vpf-10680: The file [8711 8717] has the wrong block count in the StatData (2023069) - corrected to (12222056) /Subtitles_13_English_exp.supvpf-10680: The file [8711 8756] has the wrong block count in the StatData (56800) - corrected to (54416) rebuild_semantic_pass: The entry [8711 8720] ("CONSTANTINE") in directory [758 8711] points to nowhere - is removed vpf-10650: The directory [758 8711] has the wrong size in the StatData (48) - corrected to (216) /770_8246get_next_directory_item: The entry ".." of the directory [770 8246] pointes to [741 770], instead of [2 8235] - corrected /770_8250get_next_directory_item: The entry ".." of the directory [770 8250] pointes to [741 770], instead of [2 8235] - corrected /770_8252get_next_directory_item: The entry ".." of the directory [770 8252] pointes to [741 770], instead of [2 8235] - corrected /00000.m2tsvpf-10680: The file [8252 8253] has the wrong block count in the StatData (42397720) - corrected to (42390656) /8237_8241get_next_directory_item: The entry ".." of the directory [8237 8241] pointes to [770 8237], instead of [2 8235] - corrected /8237_8243get_next_directory_item: The entry ".." of the directory [8237 8243] pointes to [770 8237], instead of [2 8235] - corrected /8711_8745get_next_directory_item: The entry ".." of the directory [8711 8745] pointes to [758 8711], instead of [2 8235] - corrected vpf-10650: The directory [8711 8745] has the wrong size in the StatData (352) - corrected to (120) /8720_8721get_next_directory_item: The entry ".." of the directory [8720 8721] pointes to [8711 8720], instead of [2 8235] - corrected rebuild_semantic_pass: The entry [8721 8735] ("JAR") in directory [8720 8721] points to nowhere - is removed rebuild_semantic_pass: The entry [8721 8736] ("META") in directory [8720 8721] points to nowhere - is removed rebuild_semantic_pass: The entry [8721 8740] ("STREAM") in directory [8720 8721] points to nowhere - is removed rebuild_semantic_pass: The entry [8721 8738] ("PLAYLIST") in directory [8720 8721] points to nowhere - is removed /CLIPINFrebuild_semantic_pass: The entry [8732 8733] ("00000.clpi") in directory [8721 8732] points to nowhere - is removed vpf-10650: The directory [8721 8732] has the wrong size in the StatData (80) - corrected to (48) rebuild_semantic_pass: The entry [8721 8737] ("MovieObject.bdmv") in directory [8720 8721] points to nowhere - is removed /BACKUPrebuild_semantic_pass: The entry [8723 8724] ("BDJO") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8729] ("PLAYLIST") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8727] ("index.bdmv") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8725] ("CLIPINF") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8728] ("MovieObject.bdmv") in directory [8721 8723] points to nowhere - is removed vpf-10650: The directory [8721 8723] has the wrong size in the StatData (184) - corrected to (48) vpf-10650: The directory [8720 8721] has the wrong size in the StatData (304) - corrected to (176) /8720_8742get_next_directory_item: The entry ".." of the directory [8720 8742] pointes to [8711 8720], instead of [2 8235] - corrected rebuild_semantic_pass: The entry [8742 8743] ("BACKUP") in directory [8720 8742] points to nowhere - is removed vpf-10650: The directory [8720 8742] has the wrong size in the StatData (72) - corrected to (48) Looking for lost files:9 /sec vpf-10670: The file [11 2335] has the wrong size in the StatData (0) - corrected to (21399552000) vpf-10680: The file [11 2335] has the wrong block count in the StatData (1665753) - corrected to (41796000) vpf-10670: The file [8711 8757] has the wrong size in the StatData (0) - corrected to (11908571136) vpf-10680: The file [8711 8757] has the wrong block count in the StatData (426936) - corrected to (23258928) vpf-10670: The file [8760 8873] has the wrong size in the StatData (3450077184) - corrected to (3480838144) vpf-10680: The file [8760 8873] has the wrong block count in the StatData (6738432) - corrected to (6798448) Flushing..finished Objects without names 20 Empty lost dirs removed 16 Dirs linked to /lost+found: 9 Dirs without stat data found 2 Files linked to /lost+found 11 Pass 4 - finished done 483076, 28 /sec Deleted unreachable items 6671 Flushing..finished Syncing..finished ########### reiserfsck finished at Mon Aug 27 01:01:39 2012 ########### All said and done, everything is up and running, my current parity check is almost finished and has only made a single correction thus far. I have a handful of items in the "lost+found" directory that I'll be sorting through tonight. The couple of Bluray movies that showed up in pass 3 will simply be deleted and re-ripped. All in all, long process, but feel much better now.
Archived
This topic is now archived and is closed to further replies.