public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kylo Ginsberg <kylo.ginsberg@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: smallest jffs2 file system possible
Date: Wed, 4 May 2005 18:38:43 -0700	[thread overview]
Message-ID: <61cc712d050504183852868c04@mail.gmail.com> (raw)

I would like to create the smallest jffs2 file system possible.  We
want to have a small separate mount point to store a small number 
(<5) of small text files (<1k each).

Empirically I've determined that this minimum size is effectively 5 *
N, where N is the physical erase block size of the underlying flash
part.  Is this correct?  Are there any workaround or patches to enable
building a smaller file system?  Is a different f/s recommended for
such an application (must be r/w, don't care about compression
particularly).

Thanks,
Kylo

             reply	other threads:[~2005-05-05  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05  1:38 Kylo Ginsberg [this message]
2005-05-05 11:05 ` smallest jffs2 file system possible 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=61cc712d050504183852868c04@mail.gmail.com \
    --to=kylo.ginsberg@gmail.com \
    --cc=kylo@kylo.net \
    --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