Df not updating
Why df command still showing 100% disk used at dev/xvda2?
Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvda2 101471352 97968944 0 100% / /dev/xvda1 101086 27568 68299 29% /boot tmpfs 2097152 0 2097152 0% /dev/shm /dev/xvdc1 154816488 101374388 45577884 69% /backup /usr/tmp DSK 495844 10858 459386 3% /tmp Edit This is what i got after running df -ih Filesystem Inodes IUsed IFree IUse% Mounted on /dev/xvda2 25M 652K 25M 3% / /dev/xvda1 26K 55 26K 1% /boot tmpfs 512K 1 512K 1% /dev/shm /dev/xvdc1 19M 497K 19M 3% /backup /usr/tmp DSK 126K 294 125K 1% /tmp Why df command still showing 100% disk used at dev/xvda2?
To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Softupdates can also effect filesystem freespace as the actual inode space recovery can be deferred; the sync(8) command can be used to encourage this to happen sooner.When the process closes the file if the reference count falls to zero the file space is marked as available.This scheme is used to avoid the Microsoft Windows type issues where it won't let you delete a file because some unspecified program still has it open.Applications may not be designed to deal elegantly with this situation and may produce inconsistent or undefined behavior when files that are in use are abruptly truncated in this manner.This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers.