Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 5
    If you are talking about the line - /dev/mapper/vg00-lv_hana_log 400G 400G 280K 100% /hana/log, you have 280 kilobytes available not gigabytes. Commented Jan 19, 2018 at 12:31
  • The problem is that du is reporting only 288 GB used, while df is reporting 400 GB used. Also when I remove files no space gets available and I can not put anything on that drive no matter that I moved more than 44 GB of data from it. Commented Jan 20, 2018 at 0:06
  • Your question is a different problem, and not a dupe in my opinion. But the problem as you say, is mystical - if there is 400gb allocated in an fs, and you delete 40gb, then 360gb will remain. The few exceptions are very rare (for example, hard links) and nearly surely don't happen in your case. Commented Jan 20, 2018 at 4:10
  • Did you, by any chance, run du before and after deleting all those files? (What were the results?) Commented Jan 20, 2018 at 5:31
  • @g-man yes I did and as I said du is reporting the size correctly, by that I mean reported size did shrink, however df size never goes down. Just a note the files are transaction logs for HANA database and they are about 1 GB in size. I thought at first HANA is keeping them opened but as you saw lsof is not reporting anything? Commented Jan 20, 2018 at 7:30