public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "zhao, forrest" <forrest.zhao@intel.com>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: luyang_ly@hotmail.com, linux-mtd@lists.infradead.org
Subject: Re: [Fwd: Re: a problem about jffs2]
Date: Fri, 11 Nov 2005 11:32:27 +0800	[thread overview]
Message-ID: <1131679947.3417.16.camel@localhost.localdomain> (raw)
In-Reply-To: <43733524.4030402@yandex.ru>


> > Dear Linus:
> > 
> > 	I recently meet a problem about jffs2.
> > 
> > 	There have three sectors in my mobilephone(OMAP730):
> > 	/dev/mtdblock3           16384      3276     13108  20% /System
> > 	/dev/mtdblock4            2048       388      1660  19% /Sysdisk
> > 	/dev/mtdblock5            5120       388      4732   8% /Appdisk
> > 
> > 	I built new file(ph_bk) in /Sysdisk dirctory. 	I write a test
> > program, as follows:
> > 	1) open it.
> > 	fd = fopen(argv[1], "r+");
> > 	2) fseek with a random number, then write a number
> > 	for (;;) {
> > 		offset = rand();
> > 		fseek(fd, offset % (1024*1024), SEEK_SET);
> > 		fwrite(&offset,sizeof(int), 1, fd);
> > 	}
> > 
> > 	I want to limit the file with 1M size, but when the test program run
> > in background,
> > 	this file maintain 1M size, but available space on /dev/mtdblock4
> > continue to reduce, as below:
> > 	Filesystem           1k-blocks      Used Available Use% Mounted on
> > 	/dev/mtdblock4            2048       512      1536  25% /Sysdisk
> > /dev/mtdblock4            2048       688      1360  34% /Sysdisk
> > 	/dev/mtdblock4            2048       792      1256  39% /Sysdisk
> > 	/dev/mtdblock4            2048       856      1192  42% /Sysdisk
> > 	/dev/mtdblock4            2048      1212       836  59% /Sysdisk
> > 	/dev/mtdblock4            2048      1516       532  74% /Sysdisk
> > 	/dev/mtdblock4            2048      1920       128  94% /Sysdisk
> > 
> > 	Is it jffs2 filesystem's bug?
> > 
I once did some testing like yours, and had the same result.

I would say that this is an intrinsic nature of JFFS2 instead of a
JFFS2's bug.
Updating 4 bytes of a file for every write operation will cause
flash space wasting since every write operation generate an 
jffs2_raw_inode + 4 bytes on flash. sizeof(jffs2_raw_inode) is 68 bytes.

Thanks,
Forrest

  reply	other threads:[~2005-11-11  3:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 11:55 [Fwd: Re: a problem about jffs2] Artem B. Bityutskiy
2005-11-11  3:32 ` zhao, forrest [this message]
2005-11-11  5:30   ` YangLu YangLu

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=1131679947.3417.16.camel@localhost.localdomain \
    --to=forrest.zhao@intel.com \
    --cc=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=luyang_ly@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox