Filesystem Check on cPanel Server

Tweet

We have had some filesystem errors on our cPanel hosting server slayer,

filesystem check is running to fix the issue, service will be back shortly.

Technical details of the process:

[root@slayer /]# fsck /dev/sdc1fsck 1.39

(29-May-2006)e2fsck 1.39 (29-May-2006)

/dev/sdc1: recovering journal

/dev/sdc1 contains a file system with errors, check forced.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structureEntry

'wp-cache-ddac63041b9632d8c83c51dd18e3fc10.meta' in /exclu/public_html/wp-content/cache/meta (5668865) has deleted/unused inode 5669909.  Clear? yes

Entry 'wp-cache-ddac63041b9632d8c83c51dd18e3fc10.html' in //public_html/wp-content/cache (5669835) has deleted/unused inode 5669854.  Clear? yes

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary informationBlock bitmap differences:  -11340456 -11341827 -(11341874--11341877) -(11341881--11341897) -11341937 -11342060 -11343872 -11346015 -(11348035--11348046) -(11348048--11348049) -11348088 -(11362359--11362365) -(11362376--11362380) -(11362392--11362397) -(11362405--11362406) -(11366827--11366831) -(11366833--11366842) -(11366973--11366978) -(11368617--11368618) -(11368743--11368754)Fix? yes
Free blocks count wrong for group #433 (9268, counted=9282).Fix? yes
Free blocks count wrong (47618001, counted=47618015).Fix? yes
Inode bitmap differences:  -5669854 -5669909 -5669917 -5669919 -5669924 -5669945 -5669979 -5669981 -5670038 -5670050 -5670385 -5670448Fix? yes

/dev/sdc1: ***** FILE SYSTEM WAS MODIFIED *****

/dev/sdc1: 118072/26214400 files (1.5% non-contiguous), 4808096/52426111 blocks

[root@slayer /]#

once the check was done, we have rebooted.

[root@slayer home2]# reboot
Broadcast message from root (pts/1) (Sat Feb  5 01:04:25 2011):
The system is going down for reboot NOW!

[root@slayer home2]# Connection to slayer.beastserv.info closed by remote host.

system got back online, everything is now stable.