Hi, I am running a dedicated server with linux cent os 5.5 32 bit with lighttpd, php 5.2.14 and mysql I am getting problem in my server. The filesystem enters read only mode automatically and then I can't edit any file in my server. This happens by itself. I tried to run fsck command and it gives the following output: [root@server]# fsck -A -y fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) /: recovering journal Clearing orphaned inode 11108656 (uid=0, gid=0, mode=0140777, size=0) Clearing orphaned inode 13631499 (uid=27, gid=27, mode=0100600, size=0) Clearing orphaned inode 13631497 (uid=27, gid=27, mode=0100600, size=0) Clearing orphaned inode 13631496 (uid=27, gid=27, mode=0100600, size=0) Clearing orphaned inode 13631495 (uid=27, gid=27, mode=0100600, size=0) Clearing orphaned inode 13631494 (uid=27, gid=27, mode=0100600, size=0) /: clean, 90929/14655488 files, 22714968/58593063 blocks Code (markup): I tried reinstalling the entire OS in my server but again after few hours I started getting problem of read only mode. I informed my hosting provider and he ran entire hdd check and told me that there is no problems found with hdd and told that it might be filesystem problem. but how can such problem arise again and again? I have used many hosting providers but I didn't had such problem earlier. So I told him to help me to fix. He replied that I should run fsck manually in rescue mode. But Anyone can tell me how to permanently fix this problem of filesystem entering read only mode again and again?? plz help me its very critical problem which is very concerning me as my sites can't run on read only mode as its dynamic site and need to write files in server when they run.. So I request to kindly help me out and tell me a good solution. Thanks.
If you have kvm, access to the server, enter single user mode (runlevel 1) then run fsck against the hdd. It should not go into read-only mode without a problem. You should never run fsck with a mounted drive or partition.
I don't have kvm access but I can have rescue mode which is single user mode I am currently running fsck in my server in rescue mode. Will it be run properly after fixing illegal blocks in rescue mode and rebooting the server?
Inodes that were part of a corrupted orphan linked list found. Fix? yes Inode 11108656 was part of the orphaned inode list. FIXED. Deleted inode 13631494 has zero dtime. Fix? yes Inode 13631495 was part of the orphaned inode list. FIXED. Inode 13631496 was part of the orphaned inode list. FIXED. Inode 13631497 was part of the orphaned inode list. FIXED. Inode 13631499 was part of the orphaned inode list. FIXED. Restarting e2fsck from the beginning... / contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Code (markup): this is the current showing me in ssh and still fixing problems.. will give more updates
Yes, it`ll if it can fix the issues. Orphaned inode means a file that takes storage but no longer exists in the filesystem itself so its clearing them out, let it do its job.
hi, I have finished running fsck in both partitions of hdd in server. then I boot up my server into normal mode and now all seems to be running fine but how can avoid similar future problems. Thanks.