[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22517: dd byte count report does not correlate with df byte count re
From: |
Assaf Gordon |
Subject: |
bug#22517: dd byte count report does not correlate with df byte count report |
Date: |
Thu, 25 Oct 2018 09:34:14 -0600 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
tags 22517 notabug
close 22517
stop
(triaging old bugs)
On Tue, Feb 02, 2016 at 12:20:36AM +0100, Bernhard Voelker wrote:
> On 02/01/2016 05:53 AM, Bob Gustafson wrote:
> >
> > Expected results:
> >
> > I would think that the sizes reported by dd and df would be comparable, but
> > they are not.
> >
> a) the MiB numbers are 1024-based, while MB are 1000-based.
>
> b) df(1) and du(1) show statistics or summaries of the data *inside*
> a file system, while the file system itself may need some space to
> manage the data. And even df/du report different sizes:
> http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#df-and-du-report-different-information
> Starting with BTRFS, the situation may even be worse (df showing
> lots of free space while BTRFS doesn't allow to create - or even
> delete - another file).
>
> Thus said: the size of the underlying device is not 100% related to
> the sizes inside the file system on that device.
> You may get the real size using e.g.
With no further comments in 2 years, I'm closing this bug.
Discussion can continue by replying to this thread.
-assaf
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#22517: dd byte count report does not correlate with df byte count report,
Assaf Gordon <=