June 11, 201412 yr Over the last week or so I've noticed that my crashplan has stopped working. I have it installed at: /mnt/cache/.permanent/crashplan The message I get is that the file system is read_only. I telnet in and sure enought I cannot create any files on /mnt/cache. I know that it works for a bit after I restart the array, because I copied a movie over to the cache drive yesterday. But at some point to becomes read-only. Any ideas on where I can go look? thanks, david
June 11, 201412 yr It sounds as if there might be some file system corruption that is causing the disk to be set read-only. To check for this you can run the command reiserfsck --check against the cache drive.
June 11, 201412 yr How do I find out which device is /mnt/cache? The unRAID web GUI tells you the device currently associated with the cache drive
June 11, 201412 yr Author Yes there is something wrong: Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Wed Jun 11 11:06:37 2014 ########### Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree.. \/ 1 (of 2|/ 2 (of 128|/ 84 (of 158|block 10682570: The level of the node (14624) is not correct, (1) expected the problem in the internal node occured (10682570), whole subtree is / 2 (of 2\/ 69 (of 104-/110 (of 155|block 5408774: The level of the node (0) is not correct, (1) expected the problem in the internal node occured (5408774), whole subtree is skipped / 80 (of 104|/ 59 (of 127\bad_path: The left delimiting key [1096 1119 0x799 DRCT (2)] of the node (16518215) must be equal to the first element's key [1037 1091 0x19678c001 IND (1)] within the node. / 90 (of 104\/124 (of 162\block 16177155: The level of the node (60601) is not correct, (1) expected the problem in the internal node occured (16177155), whole subtree is skipped / 91 (of 104|block 16179939: The level of the node (46678) is not correct, (2) expected the problem in the internal node occured (16179939), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 5 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Wed Jun 11 11:08:30 2014 So I need to run --rebuild-tree? dave
June 11, 201412 yr Author I ran: reiserfsck --rebuild-tree /dev/sdg1 It ran for a few hours then ended like this: .80%.block 37680309: The number of items (24940) is incorrect, should be (1) - corrected block 37680309: The free space (0) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 37680309, item (0): Unknown item type found [126 2781282451 0x174000131100004 (6)] - deleted ...block 39965715: The number of items (36864) is incorrect, should be (1) - corrected block 39965715: The free space (2321) is incorrect, should be (4048) - corrected pass0: vpf-10150: block 39965715: item 0: Wrong key [0 2416508928 0x911 SD (0)], deleted 100% left 0, 1479 /sec 944 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 20550800 Leaves among those 37820 - leaves all contents of which could not be saved and deleted 229 Objectids found 968 Pass 1 (will try to insert 37591 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%... left 32189, 300 /sec The problem has occurred looks like a hardware problem (perhaps memory). Send us the bug report only if the second run dies at the same place with the same block number. build_the_tree: Nothing but leaves are expected. Block 5197999 - unknown Aborted (core dumped) that doesn't look good, david
June 12, 201412 yr Author OK I ran it again, like it said and it completed successfully. However, my /mnt/cache is still read_only, even after a reboot. How do I get it to be mounted read/write like it used to be? thanks dave
June 12, 201412 yr Is there anything on it? If not, I'd take the coward's way out (or is it just expeditious brute force?) ...anyway...you could copy the valid bits from cache to your PC/MAC and reformat the cache drive. reassign it to the array.
June 12, 201412 yr Author I just ordered a new drive and will swap it out. Looks like this drive is failing anyway. thanks for all the help, david
June 13, 201412 yr Stating the obvious: When you 'swap out' the cache drive, its not parity protected and won't be rebuilt. If you have Apps or other non-Movered data on your existing cache drive, be sure to copy them off.
Archived
This topic is now archived and is closed to further replies.