From: David Woodhouse <dwmw2@infradead.org>
To: David Wuertele <dave-gnus@bfnet.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ARGH. About to write node to 0x00022fac on flash, but there's data already there
Date: Thu, 24 Jul 2003 16:59:13 -0400 [thread overview]
Message-ID: <1059080351.27746.3.camel@lapdancer.baythorne.internal> (raw)
In-Reply-To: <m3smov3b07.fsf@bfnet.com>
On Thu, 2003-07-24 at 16:50, David Wuertele wrote:
> Whenever I write big files to my JFFS2 partition, I'm getting this
> error (see Subject: line). Small files don't result in the error. I
> googled for hints but found nothing helpful. My stats:
>
> mkfs.jffs2: revision 1.32
> architecture: mipsel
> Kernel: 2.4.18 (CONFIG_JFFS2_FS=y, CONFIG_JFFS2_FS_DEBUG=2)
Upgrade to something vaguely recent -- or at least upgrade the JFFS2
code. If it still happens, set CONFIG_JFFS2_FS_DEBUG=1, log it via
serial console and show me the whole thing from (and including) mount
onwards. Have flash images from before and after available should I want
them.
--
dwmw2
prev parent reply other threads:[~2003-07-24 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 20:50 ARGH. About to write node to 0x00022fac on flash, but there's data already there David Wuertele
2003-07-24 20:59 ` David Woodhouse [this message]
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=1059080351.27746.3.camel@lapdancer.baythorne.internal \
--to=dwmw2@infradead.org \
--cc=dave-gnus@bfnet.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