From: Wouter Thielen <sauron@morannon•org>
To: linuxppc-embedded@ozlabs•org
Subject: Ext2fs on a MPC850 running BusyBox Linux and a 2.4.27 kernel
Date: Thu, 17 Mar 2005 11:53:52 +0100 [thread overview]
Message-ID: <423961C0.40704@morannon.org> (raw)
Hello,
I am trying to get a 128K read/write partition on the 4M NAND flash chip
to store configuration data for the system in ext2 format. mke2fs and
mounting works fine. The problem starts when I write to the partition: I
can write to it fine, but without proper umounting the data written
won't be saved. I tried the following things:
- mounting with -o sync
- checking the fs/ext2/* code and trying to get fs update operations to
call the functions that umount calls (ext2_put_super and
ext2_sync_super), but that only results in kernel oopses and no saved
data either.
I have been suggested to use a flash filesystem like jffs2, but the
problem is that I have only 1 block to work with. Flash filesystems
require more, jffs2 requires 6 blocks for 1 usable block and that would
be an inacceptable overhead of 83%. So I'd like to try to use ext2 (or
minixfs which is slimmer than ext2, but still has the same problem) for
that small read/write partition. Anyone got any ideas/suggestions on how
to make ext2 sync to disk after write operations in the buffer?
Wouter Thielen
MuLogic B.V. Netherlands
reply other threads:[~2005-03-17 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=423961C0.40704@morannon.org \
--to=sauron@morannon$(echo .)org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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