From: Paul van Gool <paul.vangool@rinconnetworks.com>
To: Jasmine Strong <jasmine@regolith.co.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: No space left on almost empty JFFS2 filesystem
Date: Wed, 25 Jun 2003 11:24:31 -0700 [thread overview]
Message-ID: <20030625182431.GA15901@rinconnetworks.com> (raw)
In-Reply-To: <20030625182020.GA15879@rinconnetworks.com>
Creating am image with '-e 0x10000' and running with it, results in:
# mount -t jffs2 /dev/mtdblock4 /mnt/jffs
mtdblock_open
ok
jffs2_scan_empty(): Empty block at 0x000017ac ends at 0x00010000 (with 0x200319y
CLEANMARKER node found at 0x00010000, not first node in block (0x00000000)
jffs2_scan_empty(): Empty block at 0x0002000c ends at 0x00030000 (with 0x200319y
CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)
jffs2_scan_empty(): Empty block at 0x0004000c ends at 0x00050000 (with 0x200319y
CLEANMARKER node found at 0x00050000, not first node in block (0x00040000)
jffs2_scan_empty(): Empty block at 0x0006000c ends at 0x00070000 (with 0x200319y
CLEANMARKER node found at 0x00070000, not first node in block (0x00060000)
jffs2: No clean _or_ dirty blocks to GC from! Where are they all?
jffs2: Couldn't find erase block to garbage collect!
jffs2: No clean _or_ dirty blocks to GC from! Where are they all?
jffs2: Couldn't find erase block to garbage collect!
jffs2: No clean _or_ dirty blocks to GC from! Where are they all?
jffs2: Couldn't find erase block to garbage collect!
...
Paul
On Wed, Jun 25, 2003 at 11:20:20AM -0700, Paul van Gool wrote:
> So I tried:
>
> mkfs.jffs2 --pad=0x80000 --little-endian --squash -e 0x20000 -d /home/vangool/jffs -o jffs.img
>
> thinking that that would give me 3 erase blocks but I still get the
> same error. Am I doing something wrong?
>
> Thanks.
>
> Paul
>
>
> On Wed, Jun 25, 2003 at 08:58:46AM -0700, Paul van Gool wrote:
> > On Wed, Jun 25, 2003 at 04:52:34PM +0100, Jasmine Strong wrote:
> > > JFFS2 filesystems require a certain number of erase blocks reserved for
> > > garbage collection before you can write anything to them.
> > I see. 1 Block will indeed never be enough then. Shows my ignorance ;-).
> >
> > Thanks.
> >
> > Paul
> > --
> > Paul van Gool Rincon Networks
> > paul.vangool@rinconnetworks.com (805)-705-1442
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
> --
> Paul van Gool Rincon Networks
> paul.vangool@rinconnetworks.com (805)-705-1442
--
Paul van Gool Rincon Networks
paul.vangool@rinconnetworks.com (805)-705-1442
next prev parent reply other threads:[~2003-06-25 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 15:48 No space left on almost empty JFFS2 filesystem Paul van Gool
2003-06-25 15:52 ` Jasmine Strong
2003-06-25 15:58 ` Paul van Gool
2003-06-25 18:20 ` Paul van Gool
2003-06-25 18:24 ` Paul van Gool [this message]
2003-06-25 18:29 ` Jasmine Strong
2003-06-25 18:49 ` Jörn Engel
2003-06-25 19:44 ` Paul van Gool
2003-06-25 20:03 ` Paul van Gool
2003-06-25 19:52 ` Thomas Gleixner
2003-06-25 19:43 ` Paul van Gool
2003-06-25 16:04 ` Jörn Engel
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=20030625182431.GA15901@rinconnetworks.com \
--to=paul.vangool@rinconnetworks.com \
--cc=jasmine@regolith.co.uk \
--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