From: "Sébastien Côté" <scote1@Matrox.COM>
To: Alexander Larsson <alex@cendio.se>
Cc: mtd@infradead.org
Subject: Re: ext2_lookup() and i_count
Date: Fri, 12 May 2000 15:15:59 -0400 [thread overview]
Message-ID: <391C586F.1FCE77B@matrox.com> (raw)
In-Reply-To: Pine.LNX.3.96.1000511160915.11688A-100000@biffen.cendio.se
Alexander Larsson a écrit :
>
> On Thu, 11 May 2000, David Woodhouse wrote:
>
> >
> First create your to be filesystem in a directory (call it e.g. img_dir),
> then run "mkfs.jffs img_dir > fs.jffs", this creates an image fs.jffs that
> you can copy to your flash (in the case of an mtdram flash, just do "cat
> fs.jffs > /dev/mtd0". Then mount the flash "mount -t jffs /dev/mtdblock0
> /mnt/jffs".
>
> Then just go to /mnt/jffs and play around with the filesystem. Not
> everything works well right now, rename isn't implemented, and unlink
> seems to have some problems.
I tried this out today and encoutered some problems. Most file
operations work well (cp, rm ln -s) but I have two problems.
First, big file don't get mounted on the filesystem (by big I mean a few
hundred Ks). I tried to track the problem without luck. Second, the
command df always reports dans the device is full. Since
jffs_scan_flash()'s reports are ok, I'm wondering where df takes the
informations from?
Did you run into similar problems?
Thanks,
--
Sébastien Côté
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-05-12 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <30252.958050596@devel2.axiom.internal>
2000-05-11 14:16 ` ext2_lookup() and i_count Alexander Larsson
2000-05-11 14:28 ` Sébastien Côté
2000-05-11 14:57 ` Alexander Larsson
2000-05-12 19:15 ` Sébastien Côté [this message]
2000-05-15 10:04 ` Alexander Larsson
2000-05-15 13:28 ` Sébastien Côté
2000-05-16 20:36 ` Sébastien Côté
2000-05-19 13:05 ` Alexander Larsson
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=391C586F.1FCE77B@matrox.com \
--to=scote1@matrox.com \
--cc=alex@cendio.se \
--cc=mtd@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.