0
0
The output for df -h
is:
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 196G 12G 184G 6% /
The output for df -i
is:
Filesystem Inodes IUsed IFree IUse%
Mounted on
/dev/xvda1 0 0 0 - /
The output for blkid
:
/dev/xvda1: UUID="4a1d89b1-5cd6-4716-9aab-f187108abd1a" UUID_SUB="d10faf32-6262-4f6e-adf0-fc74984bf5ed" TYPE="btrfs" PARTUUID="000cbad2-01"
/dev/xvda2: UUID="199566f6-8820-4077-9587-f64530eff0ca" TYPE="swap" PARTUUID="000cbak2-02"
Also had observed that killing the process from the output of lsof / | grep deleted
was bringing down the usage of disk from 100% to as low as 20% (a random number) but I am not sure if it is releasing the space.
Still getting the error:
cp: cannot create regular file ‘/etc/abc/apps’: No space left on device.
I am posting the question for the first time. Not sure what all might be the requirements. Let me if any further information is required
3The 0 inodes isn't a problem in this case. BTRFS is... very different. It's a common problems for
df
to give inaccurate results. Instead trysudo btrfs filesystem usage /
. – Cliff Armstrong – 2019-02-07T06:20:47.317I didn't even notice the BTRFS in the Q, off to the side there in the blkid output, it should be more prominent, I'll edit – Xen2050 – 2019-02-07T09:07:23.997
Thanks for the prompt response.Later I googled for the bugs reported for btrfs and found that there is a bug where it shows that btrfs gives No disk space even when df -h does not say so.The following is the link. https://btrfs.wiki.kernel.org/index.php/Problem_FAQ
– Nidhi – 2019-02-08T08:38:20.997