public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Esteban Lopez <elopez@softel.net.mx>
Cc: linux-mtd@lists.infradead.org
Subject: Re: df -h, du -ahx and flash size not match
Date: Wed, 07 Mar 2012 19:30:02 +0200	[thread overview]
Message-ID: <1331141402.3463.34.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4F435C55.9000402@softel.net.mx>

On Tue, 2012-02-21 at 08:56 +0000, Esteban Lopez wrote:
> I read the UBIFS FAQ and UBIFS documentation but all the explanation
> is about free space. I don't understand why df -h reports 236M of
> total space if I have 469762048 bytes in this partition.

I think it is also around the same set of issues. Because we do not in
advance what kind of data the FS will be holding and how it is written,
we do not really know how much data can fit to the FS. So UBIFS makes
pessimistic calculations and reports its size as the absolutely minimum
amount of space which it can fit in the worst case scenario. So in your
case UBIFS decides that in the worst case it can fit a 236M file of
uncompressible data (e.g., a movie).

This is kind of a compromise. Imagine UBIFS reported 500MiB free space,
then you write a 300MiB AVI movie, and it does not fit. So we prefer to
report the absolute minimum.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2012-03-07 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 17:41 df -h, du -ahx and flash size not match Esteban Lopez
2012-02-20 23:47 ` Brian Norris
2012-02-21  8:56   ` Esteban Lopez
2012-03-07 17:30     ` Artem Bityutskiy [this message]
     [not found]   ` <4F45FE0C.3070807@softel.net.mx>
2012-02-23 19:35     ` Brian Norris
2012-02-23 16:52       ` Esteban Lopez

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=1331141402.3463.34.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=elopez@softel.net.mx \
    --cc=linux-mtd@lists.infradead.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