June 10, 201016 yr went to copy some data to the array this morning and found it was mounted as read-only. found this in the syslog: Jun 9 03:40:21 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 Jun 9 03:40:21 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 219031116. Fsck? Jun 9 03:40:21 Tower kernel: REISERFS (device md1): Remounting filesystem read-only Jun 9 03:40:21 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [34928 34929 0x0 SD] Is that a temporary thing that I shouldn't worry too much about? I've stopped and started the array and it seems ok now.... Cheers, Justin
June 10, 201016 yr Author Oh and when restarting the array it took a long time to mount one of the disks. I assume that was due to checking the filesystem etc: Jun 10 08:03:47 Tower kernel: REISERFS (device md1): replayed 611 transactions in 117 seconds
June 10, 201016 yr You need to perform a file-system check on that disk. It probably is need of repair. The corruption has just not yet been encountered since you rebooted. See the wiki instructions here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
June 10, 201016 yr Author looks like everything is ok Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jun 10 22:31:49 2010 ########### Replaying journal.. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 196693 Internal nodes 1263 Directories 1119 Other files 15133 Data block pointers 197077236 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Thu Jun 10 23:38:55 2010 ###########
June 10, 201016 yr I've never seen file-system errors go away on their own, although I suppose it could if you had deleted the file involved. Also possible would be the re-playing of the un-committed transactions took care of it for you... But... there is the remote possibility that a memory error caused it to think the file-system was corrupted when it was not. I would run a memory check, preferably overnight, just to be sure. It is re-assuring that the file-system is healthy though. Joe L.
Archived
This topic is now archived and is closed to further replies.