public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Sergei Poselenov <sposelenov@emcraft.com>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: real free capacity of the partition
Date: Mon, 07 Jul 2008 20:15:46 +0400	[thread overview]
Message-ID: <48724132.3050004@emcraft.com> (raw)
In-Reply-To: <486CFB83.3010301@emcraft.com>

Hello all,

Seems I found why is that happens.
In jffs2_statfs() the wasted_size is excluded
from calculation:
...
    avail = c->dirty_size + c->free_size;
...

Could someone explain for what reason?
Have I understand it right - on the certain conditions, the
wasted space can be converted to dirty space?

Regards,
Sergei

Sergei Poselenov wrote:
> Hello,
> 
> Probably this is a trivial question and won't take much of your time.
> 
> A simple test on a JFFS2 partition:
> 
> # df
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/mtdblock1            1024       376       648  37% /etc
> # dd if=/dev/urandom of=tmp bs=1024 count=2900
> dd: tmp: No space left on device
> # rm tmp
> # df
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/mtdblock1            1024       372       652  36% /etc
> 
> Why additional space appeared?
> 
> I've noted, that this effect:
> - appeared only on the well-used partition, not on the
>   fresh-created one.
> - appeared only after filling up the device
> - appeared only once. On subsequent tests, the free space was
> reported without magic increases.
> 
> 
> Is this is an effect of the JFFS2 garbage collector?
> Is there any method to learn the real available capacity of the
> mounted partition?
> 
> Thanks in advance,
> Sergei
> 

  reply	other threads:[~2008-07-07 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 16:17 JFFS2: real free capacity of the partition Sergei Poselenov
2008-07-07 16:15 ` Sergei Poselenov [this message]
2008-07-11 17:32   ` David Woodhouse

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=48724132.3050004@emcraft.com \
    --to=sposelenov@emcraft.com \
    --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