Correcting an inconsistent filesystem
Hi there --
One of our servers is running the Fedora Core 14 64-bit distribution with a MySQL database and Apache webserver-based application. The server also runs a virtual machine via the Virtualbox application. The operating system here is Ubuntu 10.04 LTS 64-bit distribution, and it also runs a MySQL database and Apache webserver-based application. The / filesystem of the Fedora system is suspected of being in an inconsistent state. While the server appears to be running without issue, the backup software that is used on a nightly basis is able to backup the /boot, but not the / filesystem. A problem such as this tends to indicate an inconsistency. Is there a way to check for an inconsistency of the / filesystem without adversely affecting either the host or virtual machine? Also, if a problem is found, what is the command syntax to correct it, and will it potentially cause problems with either server? Thanks. |
May depend on f/s type. Also is / "just" the system (i.e. do you have other mount-points for things like /var, /usr, ...)
Short answer is probably "this could get ugly". For ext[234] you can't reliably fsck the filesystem whilst it's mounted. So that means a re-boot - I'm guessing that qualifies as adversely affecting that server software. From another system you could run "fsck -n" after it is down. That might give you some idea of any problems, although what good that would be might be moot. "Fixing" the problems may result in a consistent f/s, but broken files. Then maybe you could use that info - but if you don't have recent backups ... erk Edit: forgot to ask ... why are you running server(s) on fedora ?. Especially an LTS guest ... Seems arse-about to me ... |
All times are GMT -5. The time now is 02:32 PM. |