All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier DEBREUIL <xde@inventel.fr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Martin Gadbois <martin.gadbois@colubris.com>,
	linux-mtd@lists.infradead.org
Subject: Re: unable to modify jffs2
Date: Tue, 12 Jun 2001 18:38:55 +0200	[thread overview]
Message-ID: <3B26459F.1F275CB1@inventel.fr> (raw)
In-Reply-To: 7905.992363355@redhat.com

David Woodhouse a écrit :
> 
> xde@inventel.fr said:
> >  jffs2_reserve_space(): Requested 0x2c bytes
> >  jffs2_reserve_space(): alloc sem got
> > Short on space, but total dirty size 0x0000002c < sector size 0x00020000, so -ENOSPC
> 
> Looks like your filesystem is too full. You need at least 5 erase blocks
> free. How big was the jffs2 image you put on it?
> 
> --
> dwmw2

In my last email :

  but something is strange since df indicates that there is no space
left
  on that fs ; but the file I have written on my 2Meg partition was only
  1.5Meg
  /mnt/jffs2/jffs2_1/usr/arm/arm-linux # df
  Filesystem           1k-blocks      Used Available Use% Mounted on
  /dev/ram0                 3963      2997       966  76% /
  /dev/mtdblock1            2048      2048         0 100%
  /mnt/jffs2/jffs2_1
  /dev/ram1                 2011        13      1998   1%
/mnt/ramdisk/rd1


So if you say that it needs at least 5 free blocks, it means that I need
5 blocks of 128KB, so at least 650KB free!!!
Is it necessary ?

In fact if this is true, a 2MB partition is to short...

Xavier

  reply	other threads:[~2001-06-12 16:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07  9:04 HELP Abraham vd Merwe
2001-06-07  9:35 ` HELP David Woodhouse
2001-06-07  9:43   ` HELP Abraham vd Merwe
2001-06-07 14:30     ` HELP Nicolas Pitre
2001-06-07  9:44   ` HELP David Woodhouse
2001-06-07  9:47     ` HELP Abraham vd Merwe
2001-06-07 17:21     ` HELP Russ Dill
2001-06-07 20:01     ` HELP David Woodhouse
2001-06-11 16:04       ` problem with zlib.o Xavier DEBREUIL
2001-06-12  8:14       ` David Woodhouse
2001-06-12  9:19         ` problem with util Xavier DEBREUIL
2001-06-12 11:36           ` unable to mount jffs2 Xavier DEBREUIL
2001-06-12 12:19           ` David Woodhouse
2001-06-12 12:30             ` Xavier DEBREUIL
2001-06-12 12:35             ` David Woodhouse
2001-06-12 13:56               ` Xavier DEBREUIL
2001-06-12 15:19                 ` unable to modify jffs2 Xavier DEBREUIL
2001-06-12 15:31                   ` Martin Gadbois
2001-06-12 15:46                   ` David Woodhouse
2001-06-12 16:26                     ` Xavier DEBREUIL
2001-06-12 16:29                     ` David Woodhouse
2001-06-12 16:38                       ` Xavier DEBREUIL [this message]
2001-06-12 16:43                       ` David Woodhouse
2001-06-12 17:21                         ` Xavier DEBREUIL
2001-06-12 21:10                         ` David Woodhouse
2001-06-12 12:36             ` unable to mount jffs2 Xavier DEBREUIL
2001-06-07  9:48   ` HELP David Woodhouse
2001-06-07  9:51     ` HELP Abraham vd Merwe
2001-06-07 10:16     ` HELP David Woodhouse
2001-06-07 14:23   ` HELP Nicolas Pitre
2001-06-12 15:20 unable to modify jffs2 Frederic Giasson

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=3B26459F.1F275CB1@inventel.fr \
    --to=xde@inventel.fr \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.gadbois@colubris.com \
    /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.