February 7, 201115 yr Hi, I've been running 4.5.1 for some time now but I've hit an issue. I got a red dot on disk 13, so I whipped it out stuck a new drive in and followed the procedure for data rebuild. All went well and the ball went green again. I did notice that my disk10 had a large error count after it after the rebuild and the file system was in read only mode, o I did it all again. Whipped out 10 and rebuild. Perfect. But my file system is still read only and my syslog has the entry Feb 8 04:58:13 Tower kernel: REISERFS (device md13): Removing [216 1257 0x0 SD].. Feb 8 04:58:13 Tower kernel: REISERFS error (device md13): vs-15011 reiserfs_release_objectid: tried to free free object id (1257) Feb 8 04:58:13 Tower kernel: REISERFS (device md13): Remounting filesystem read-only Feb 8 04:58:13 Tower kernel: done Feb 8 04:58:13 Tower kernel: REISERFS (device md13): There were 1 uncompleted unlinks/truncates. Completed So, any ideas as I need to be able to write to my array again :-) http://pastebin.com/n7qs9Lrc
February 7, 201115 yr Hi, I've been running 4.5.1 for some time now but I've hit an issue. I got a red dot on disk 13, so I whipped it out stuck a new drive in and followed the procedure for data rebuild. All went well and the ball went green again. I did notice that my disk10 had a large error count after it after the rebuild and the file system was in read only mode, o I did it all again. Whipped out 10 and rebuild. Perfect. But my file system is still read only and my syslog has the entry Feb 8 04:58:13 Tower kernel: REISERFS (device md13): Removing [216 1257 0x0 SD].. Feb 8 04:58:13 Tower kernel: REISERFS error (device md13): vs-15011 reiserfs_release_objectid: tried to free free object id (1257) Feb 8 04:58:13 Tower kernel: REISERFS (device md13): Remounting filesystem read-only Feb 8 04:58:13 Tower kernel: done Feb 8 04:58:13 Tower kernel: REISERFS (device md13): There were 1 uncompleted unlinks/truncates. Completed So, any ideas as I need to be able to write to my array again :-) http://pastebin.com/n7qs9Lrc You need to repair the file system on that /dev/md13 device as described in the wiki: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
February 7, 201115 yr Author You need to repair the file system on that /dev/md13 device as described in the wiki: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Figured, but given disk 13 is brand new and this seems to be the same error reported on the replaced drive, would the actual error have been replicated out of parity during the data rebuild?
February 7, 201115 yr You need to repair the file system on that /dev/md13 device as described in the wiki: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Figured, but given disk 13 is brand new and this seems to be the same error reported on the replaced drive, would the actual error have been replicated out of parity during the data rebuild? Yes, the "simulated" contents of the disk you re-constructed had the same corruption. Replacing the disk that was "read-only" and re-constructing onto a replacement resulted in the exact same corruption on the replacement. Did not matter if it was new or not. Joe L.
February 7, 201115 yr Author Excellent, running the checks now. Will report back once complete. Many thanks once again.
February 8, 201115 yr Author Had to do a --rebuild-tree on disk13 and all cool once again. Many thanks.
.thumb.jpeg.397929698679250607c4a4bf7a9b0102.jpeg)
Archived
This topic is now archived and is closed to further replies.