How to find cause of main file system going to read only mode
Posted
by
user606521
on Server Fault
See other posts from Server Fault
or by user606521
Published on 2013-10-22T07:59:02Z
Indexed on
2013/10/22
9:59 UTC
Read the original article
Hit count: 532
Ubuntu 12.04
File system goes to readonly mode frequently.
First of all I have read this question file system is going into read only mode frequently already.
But I have to know if it's not caused by something else than dying hard drive
. This is server provided by my client and I am just runing there some node.js workers
+ one node.js server
and I am using mongodb
.
From time to time (every 20-50h) system suddenly makes filesystem read only, mongodb process fails (due read-only fs) and my node workers/server (which are started by forever
) are just killed.
Here is the log from dmesg - I can see there some errors and messages that FS is going to read-only, and there is also some JOURNAL error but I would like to find cause of those errors..
http://speedy.sh/Ux2VV/dmesg.log.txt
edit
smartctl -t long /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.5.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
SMART support is: Unavailable - device lacks SMART capability.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
What I am doing wrong? Same is for sda2
.
Morover now when I type any command that not exists in shell I get this:
Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:
© Server Fault or respective owner