Read-only file system
This is now the second time this has happened to me. When I logged into my server this morning, I noticed that everything was running in read-only. Even as root, I couldn't delete or modify a single file. When I tried to delete a file, i would get the following message after being told that I am unable to delete the file:
"Read-only file system" Anyone have a clue why this is happening? Yesterday everything was working just fine. The first time, I thought it was just a fluke. But since this is the second time it has happened, I want to figure out what is causing it. Any idea? |
Just a WAG but if there is a filesystem error it might get remounted read only, check the options in /etc/fstab.
Also check the logs for any errors. |
can you give me an idea of what i'm looking for in the logs?
|
Could it be b/c my harddrive is full? If so, how would i find out if it is indeed full and then find out what file is taking up all the space.
The reason I ask this is b/c in one partition, I can read/write files all I want. Here is my partition table: Disk /dev/hda: 120.0 GB, 120000000000 bytes 255 heads, 63 sectors/track, 14589 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 83 Linux /dev/hda2 14 10212 81923467+ 83 Linux /dev/hda3 10213 10277 522112+ 82 Linux swap /dev/hda4 10278 14589 34636140 5 Extended /dev/hda5 10278 10282 40131 b Win95 FAT32 /dev/hda6 10283 14589 34595946 b Win95 FAT32 In /dev/hda6 I can create and write files. In /dev/hda2, I cannot. Does this help? |
strange...
When i finally stuck a monitor onto my server, i noticed that the following error message was being written across the screen repeatedly:
"EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted" What the heck does that mean - I assume it is not good. |
anybody got a clue?
|
All times are GMT -5. The time now is 10:54 PM. |