Bug 1371558 - Machine reporting disk full in 'df -h', but 'du -sh' on '/' doe not match
Summary: Machine reporting disk full in 'df -h', but 'du -sh' on '/' doe not match
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 13:10 UTC by Miheer Salunke
Modified: 2019-12-16 06:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-25 20:01:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Miheer Salunke 2016-08-30 13:10:40 UTC
Description of problem:

We experienced our disk filling which is usually because of Docker logs, which we rectified and rebooted the machine (to clear any open files held by processes). When coming back up the machine the machine still reports 100% full (although ~200MB is free). 'du -sh' reports '/' to be using around 5GB in total. We have also tried mounting '/' to another directory and running 'du -sh' again here but no luck.

Are there any other checks we could perform?


Version-Release number of selected component (if applicable):
OpenShift Enterprise 3.1

How reproducible:
Always on customer end

Steps to Reproduce:
1.Mentioned in the description
2.
3.

Actual results:


Expected results:


Additional info:
Mail thread in aos-devel and openshift-sme with subject "Machine reporting disk full in 'df -h', but 'du -sh' on '/' doe not match"

Comment 1 Eric Paris 2016-08-31 13:09:21 UTC
df and du are not typically expected to match.

du sums up the size of each file and shows the total. But remember, on disk, things are in chunks of block size (4k). So a file with 1 byte will take (at least) 4k of disk space. So du will show 1 byte while df will show 4k used.

Comment 2 Derek Carr 2016-10-25 20:01:02 UTC
Miheer, I don't see anything that is actionable in this bug report.  I am going to close as not a bug, and feel free to re-open if there is a misunderstanding on my part.


Note You need to log in before you can comment on or make changes to this bug.