df -kh does not update the correct disk space usage
I have a problem with 'df' (Disk Free) command.
Yesterday, i was moving a 20GB DB (MySQL - InnodDB) from /var/lib/mysql (which is 90% full - 5GB free space left) to /var3 partition.
After i've successfully moved the DB to /var3 and made a symlink from /var/lib/mysql to the /var3, the DB was tested working fine.
But the problem occurs when i used 'df -kh' to check the free space again where /var/lib/mysql still occupying the same disk space like the DB has NOT been moved to the new partition which is /var3.
I left it for couple of days when my /var/lib/mysql gets critical level again last night to 98% (free space left 2.5GB).
I decided to reboot my server.
Just plainly rebooting my server, and when it comes up, 'df -kh' shows /var/lib/mysql has 20G more free space!!!
The nightmare comes, my DB (MySQL - innodb engine) crashes.
Anyway, we have to restore all data again to the crashed DB. But what surprised me was, why was i 'rebooting' the server to 'free' the disk space but would actually caused a crash to my DB??
Anyone? Any experience on this?
refer these for further knowledge
Thanks for your post, it raised my concern about open files on the system and have learned a lesson thought.
|All times are GMT -5. The time now is 08:04 AM.|