Read-only is Linux’s protection mechanism or defensive mechanism. If the OS detects that data is now being written correctly (Bad Data) then the OS will throw itself into read-only. This does two things, 1) it prevents and more data from being written..both good and bad data. 2) It will get the user or admins attention much quicker.
Try to create a file first you should get something like this:
-bash: file: Read-only file system
If you are not sure how to create a file, simply run “$ mount” .
$ mount | grep ‘/ftpusers’
For this next part, you will need to be root. This way you can modify the file system
$ sudo -i
$ mount -o remount,rw /ftpusers/tmp
This will remount the file system in a read-write. Once done setting the file system back to default. simply type exit and you will return to being a normal user.
As with any commands, if you would like to know what options you have. simply add -h or –help at the end of it.
If you ever get this error, “Could not open log file: /var/log/UcliEvt.log” Chances are that your system is in read only mode. Here is how to correct that wee problem.
mount -t tmpfs none /var/lock
If you haven’t tried this already, check the file system with “fsck”.
This will fix some of the bad writes and allow the filesystem to be mounted. On the subsequent run, it will fix more issues. Mostly issues thate were dependent on the major fixes. (think of the first run a prerequisite to the second time running “fsck”)
You, and the customers should always make sure to have a backup of good fsck, for various reasons. As with all data, everyone should always back up their data.