johnodon Posted October 14, 2014 Share Posted October 14, 2014 I don't think this is beta related but I am on v6b10a. I'm trying to cleanup all of my metadata since I plan on moving away from MCM to MB and I ran into a snag. I am unable to delete all of these movie.xml files on disk9 (/dev/sdm) root@unRAID:/mnt/disk9/Movies/300# ls -l total 24 -rw-rw-rw- 1 nobody users 22976 Dec 10 2013 movie.xml root@unRAID:/mnt/disk9/Movies/300# rm movie.xml rm: cannot remove ‘movie.xml’: Read-only file system Searching has pointed me to running reiserfsck and this is as far as I made it: root@unRAID:/mnt# reiserfsck --check /dev/sdm reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/sdm Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/sdm. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. The wiki states to NOT run the rebuild-sb option without asking in the forum first. So, that is why I am here. EDIT: I just tried to run a --check on a few of the other drives and I get the same message on each. EDIT: And of course I read the rest of the wiki and saw this: "If you get an error that says reiserfs_open: the reiserfs superblock cannot be found on /dev/sdX. Failed to open the filesystem. it usually indicates you attempted to run the file system check on the wrong device name. For almost all repairs, you would use /dev/md1, /dev/md2, /dev/md3, /dev/md4, etc. If operating on the cache drive that is not protected by parity you would use /dev/sdX1 (note the trailing "1" indicating the first partition on the cache drive)" How do you determine the /dev/md# of the drive in question? Is the # the same as the # assigned by unraid in the webgui? EDIT: NM...found the answer. I'm running a check now and will post the results if needed. John Link to comment
johnodon Posted October 14, 2014 Author Share Posted October 14, 2014 root@unRAID:/mnt# reiserfsck --check /dev/md9 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md9 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 Tue Oct 14 11:35:10 2014 ########### Replaying journal: Trans replayed: mountid 125, transid 272813, desc 6465, len 1, commit 6467, next trans offset 6450 Trans replayed: mountid 125, transid 272814, desc 6468, len 1, commit 6470, next trans offset 6453 Trans replayed: mountid 125, transid 272815, desc 6471, len 1, commit 6473, next trans offset 6456 Trans replayed: mountid 125, transid 272816, desc 6474, len 1, commit 6476, next trans offset 6459 Trans replayed: mountid 125, transid 272817, desc 6477, len 1, commit 6479, next trans offset 6462 Trans replayed: mountid 125, transid 272818, desc 6480, len 1, commit 6482, next trans offset 6465 Replaying journal: Done. Reiserfs journal '/dev/md9' in blocks [18..8211]: 6 transactions replayed Checking internal tree.. \/ 3 (of 18\/113 (of 154\/104 (of 170\bad_indirect_item: block 478576642: The item (164 165 0x4dc4a001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (541) to the block (478575373), which is in tree already / 6 (of 18//120 (of 152\/101 (of 154|bad_indirect_item: block 485655026: The item (1533 1608 0x1 IND (1), len 12, location 1400 entry count 0, fsck need 0, format new) has the bad pointer (2) to the block (452989850), which is in tree already / 9 (of 18-/ 16 (of 169\/ 47 (of 170-bad_indirect_item: block 462187125: The item (2707 3407 0x6dd9c001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (446) to the block (462188382), which is in tree already / 18 (of 18// 75 (of 163|/102 (of 170-bad_indirect_item: block 224769856: The item (5410 5529 0x2b03a001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (486) to the block (267780097), which is in tree already finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Checking Semantic tree: finished 6 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Tue Oct 14 12:03:10 2014 ########### Running --fix-fixable now. Link to comment
johnodon Posted October 14, 2014 Author Share Posted October 14, 2014 Finished. root@unRAID:/mnt# reiserfsck --fix-fixable /dev/md9 reiserfsck 3.6.24 Will check consistency of the filesystem on /dev/md9 and will fix what can be fixed without --rebuild-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 ########### reiserfsck --fix-fixable started at Tue Oct 14 12:03:59 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md9' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. \/ 3 (of 18\/113 (of 154\/104 (of 170\bad_indirect_item: block 478576642: The item (164 165 0x4dc4a001 IND (1), len 4048, location 48 entry count 0, fsck need 0, formt new) has the bad pointer (541) to the block (478575373), which is in tree already - zeroed / 6 (of 18//120 (of 152\/101 (of 154bad_indirect_item: block 485655026: The item (1533 1608 0x1 IND (1), len 12, location 1400 entry count 0, fsck need 0, format new) has the bad pointer (2) to the block (452989850), which is in ree already - zeroed / 9 (of 18-/ 16 (of 169\/ 47 (of 170bad_indirect_item: block 462187125: The item (2707 3407 0x6dd9c001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (446) to the block (462188382), whih is in tree already - zeroed / 18 (of 18// 75 (of 163|/102 (of 170bad_indirect_item: block 224769856: The item (5410 5529 0x2b03a001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (486) to the block (267780097), whih is in tree already - zeroed finished Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later. Checking Semantic tree: /Movies/Red 2/Red 2.mkvvpf-10680: The file [164 165] has the wrong block count in the StatData (60714152) - corrected to (60714144) (781/Images /The Smurfs 2/The Smurfs 2.mkvvpf-10680: The file [2707 3407] has the wrong block count in the StatData (31729040) - corrected to (31729032) /How the Grinch Stole Christma/Movies/Meet the Parents/Meet the Parents.nfovpf-10680: The file [1533 1608] has the wrong block count in the StatData (24) - corrected to (16) finished No corruptions found There are on the filesystem: Leaves 434304 Internal nodes 2649 Directories 719 Other files 4887 Data block pointers 438206519 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Oct 14 12:37:40 2014 ########### Link to comment
JonathanM Posted October 14, 2014 Share Posted October 14, 2014 Finished.Run check again to see if it all got fixed. Link to comment
johnodon Posted October 14, 2014 Author Share Posted October 14, 2014 Yeah, going to do that later. I jumped the gun and called the wife and told her she can watch her show again. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.