linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 53741] New: Used block count in df output
Date: Wed, 13 Feb 2013 05:15:23 +0000 (UTC)	[thread overview]
Message-ID: <bug-53741-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=53741

               URL: http://marc.info/?l=linux-ext4&m=136021915127138&w=2
           Summary: Used block count in df output
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.32
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: mujeeb.adil@gmail.com
        Regression: No


I have an observation on EXT4 filesystem. I created filesystem of size
1TB, 4TB, and 7TB and then checked the output of df command.

df command showed the number of 1KB blocks used. The result was:
1TB: 204056
4TB: 198680
7TB: 181784

I performed the same on XFS and the result was:
1TB: 32928
4TB: 32928
7TB: 33024

EXT4 result shows with increasing filesystem size, the number of used
blocks decreased. This looks odd.

>From the linux-ext4 mailing list discussion
(http://marc.info/?l=linux-ext4&m=136021915127138&w=2), it seems to be a bug in
df reporting.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2013-02-13  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13  5:15 bugzilla-daemon [this message]
2013-02-13  5:21 ` [Bug 53741] Used block count in df output bugzilla-daemon
2013-11-18 15:39 ` bugzilla-daemon
2013-11-18 15:39 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-53741-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).