AnsweredAssumed Answered

disk failure with no faileddisk.log

Question asked by matt on Nov 1, 2011
Latest reply on Nov 30, 2011 by matt
I currently have a node that is failed due to a "Disk Failure(s)" alarm.  It says to look at /opt/mapr/logs/faileddisk.log but that file doesn't exist.  The Dashboard says the three disks are offline, and that they are 100% full. The mfs.log file has an ominous error on startup that may help make sense of the situation, but I don't fully understand what it means, I'd appreciate some insight:


`2011-11-01 15:45:42,1033 INFO IOMgr fs/server/io/iomgr.cc:1202 clnt x.x.0.0:0 req 0 seq 0 SP1:0 /dev/sdb
2011-11-01 15:45:42,1033 INFO IOMgr fs/server/io/iomgr.cc:1202 clnt x.x.0.0:0 req 0 seq 0 SP1:1 /dev/sdc
2011-11-01 15:45:42,1033 INFO IOMgr fs/server/io/iomgr.cc:1202 clnt x.x.0.0:0 req 0 seq 0 SP1:2 /dev/sdd2011-11-01 15:45:42,1033 INFO IOMgr fs/server/io/spinit.cc:231 clnt x.x.0.0:0 req 0 seq 0 Read SP Superblock
2011-11-01 15:45:42,1036 ERROR IOMgr fs/server/io/spinit.cc:286 clnt x.x.0.0:0 req 0 seq 0 SP(SP1) Marked with ERROR(22), hence failing online`

Outcomes