All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Weber <tweb@peppercon.de>
To: linux-mtd@lists.infradead.org
Subject: Guaranteed writable space on JFFS2?
Date: Thu, 20 Jan 2005 13:55:20 +0100	[thread overview]
Message-ID: <41EFAA38.3010903@peppercon.de> (raw)

Hi,

I've a problem with JFFS2 (kernel 2.4.26) on a NOR flash with 128k blocks.
Due to previous unexpected behaviour, I've already changed

> super.c@85:
> -       avail = c->dirty_size + c->free_size;
> +       avail = (c->dirty_size / c->sector_size) * c->sector_size + c->free_size;

as GC returns ENOSPC on dirty size < sector size. This occurs quite 
often on a nearly full fs with 128k blocks.
By now, e.g. df provides the physical free space, but I do not know how 
much of this space is really writable, since I do not know how much is 
necessary file system organisation, inodes, etc.
Is there a way to predict the maximum file size, which will still be 
writable?

Thanks for your suggestions,
Thomas

             reply	other threads:[~2005-01-20 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 12:55 Thomas Weber [this message]
2005-01-21  9:39 ` Guaranteed writable space on JFFS2? Artem B. Bityuckiy

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=41EFAA38.3010903@peppercon.de \
    --to=tweb@peppercon.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.