I have a vps with file system trouble and the provider has been unable to fix it.
If /dev/simfs is missing on a clean install (CentOS 5.5), and not created later, will this cause serious problems with a file system using (Root filesystem) SIMFS
Location = /dev/simfs ??
The obvious answer (to me) would be YES, this is a serious problem.
I have 3 VPS's: The two "good" ones use / (Root filesystem) Reiser Filesystem (reiserfs) by default and the Location = /dev/simfs
The location /dev/simfs DOES show an empty file (container / whatever), and the systems work great.
The "bad" VPS shows / (Root filesystem) SIMFS and the Location = /dev/simfs.
The location /dev/simfs does NOT show anything there.
The provider claimed to have "fixed" the config file on my container, but it is still giving out a nightmare of file errors, SSH blocks all connections, etc.
After reboot everything is OK for ~30 minutes, and then it all Melts-Down again.
If '/dev/simfs' is missing (CentOS 5.5) will this cause serious problems with a file system using (Root filesystem) SIMFS Location = /dev/simfs ??
How can I teach my provider to fix this?
Best Answer
There is nothing wrong whatever the fstab or the mtab contains.
So
/dev/simfsand different variations means nothing wrong. If the host itself has filesystem or I/O problems the guest (your vps) will suffer, but this is not related to what you see in themountcommand output.