=========== 1. # umount /dev/hda1 Now change the file system type to ext2 by typing the following command 2. # tune2fs -O ^has_journal /dev/hda1 Verify that there are no error: 3.# e2fsck -y /dev/hda1 Mount the file system to original mount point (for example /home or /mnt): 4. # mount -t ext2 /dev/hda1 /home Go to mount point and remove .journal file 5. # rm -f .journal ===========
The ext2 or second extended filesystem is a file system for the Linux kernel, and the ext3 is a journaled file system. The ext3’s main advantage over ext2 is journaling which improves reliability and eliminates the need to check the file system after an unclean shutdown. Journaling process file system log convert file system during disk, if any problem arise it will be reconstructed it will be done by tune2fs tune to ext3 file system,While the power failure occur, Journalism File system restore pre-crash data store on the disk. It will also restore unsaved data.
========
unmount hda1 and tune it by journel like :
tune2fs -c 0 -i 30 -j /dev/hda1
then mount it. ========
c : number of mounts after which the filesystem will be checked by e2fsck. If it's is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck and the kernel
i : Adjust the maximal time between two filesystem checks. Use it with c option.
If you get this type of error message, please check the server's firewall first. I have faced this error message during connecting to the FTP server. In my case passive ports ranges were not enabled in the FTP and iptables firewall.
==== PassivePortRange 30000 50000 ====
Add the above line in the ftp configuration file and enable them in the iptables like :
===== iptables -A INPUT -p tcp --destination-port 30000:50000 -j ACCEPT iptables -A OUTPUT -p tcp --source-port 30000:50000 -j ACCEPT =====
Then restart iptables and ftp server like :
==== service iptables restart /etc/init.d/pure-ftpd restart ====
If above solutions don't work please configure CSF+LFD firewall on the server and stop iptables. This will solve the problem.
Another important point is that you may connect to the server through "active mode [server will connect to the client]" through the FTP client(like filezilla). Just enable the option a the FTP client and retry to connect. That's it.
A core file records memory image of running process.when a php process is killed, apache creates core files under your account.These core files takes too much of space on server.There is no harm on deleting these files.You can get rid off these core files by modifying the httpd start up file.
======= vi /usr/sbin/httpd and ulimit -c 0 after the first "ulimit" counting from the last. =======
I got this error messages from munin monitoring service and following was the error messages :
========= eth0 errors WARNINGs: packets is 1.52 (outside range [:1]). =========
So, my basic concept is either eth0 is being overloaded or isn't compatible with kernel or OS. So, I checked the settings of the eth0 and RX(receive) and TX(transmit) packet errors and I found that there is error at RX. I have pasted the results here.
I contacted the owner of the server and he assured me that the maximum speed of the NIC is 1GB/sec. So, I increased it using the following command and that fixed the notification error messages:
================== root@server [~]#ethtool -s eth0 speed 1000 duplex full ==================