public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "John Hall" <john-news1@cambridgetechgroup.com>
To: linux-mtd@lists.infradead.org
Subject: Lost space on JFFS2 partition
Date: Thu, 28 Aug 2003 10:50:38 +0100	[thread overview]
Message-ID: <6306.3f4dd070.667ee@irwin2.crw.uk.net> (raw)

Hi,

I have a 7MB NAND flash partition, on which I'm running JFFS2. This
partition contained about 3.5MB of files, yet df reported that the partition
was 96% full. I tried sending SIGHUP to the gc thread and unmounting and
remounting the device, but it had no effect. I then moved the files off the
partition and then copied them back, and the usage went down to just 31%,
which with compression is what one would expect.

I've got two ideas about what happened:

1. The files in question are log files and so there are lots of small writes
happening. How does JFFS2 compress files? Is it on a block basis or per
write? If it is the latter then I could imagine that compression is actually
having an adverse effect when a file is created from a large number of small
writes.

2. A bug in JFFS2 was causing some unused space not to be garbage collected.
The version of JFFS2 being used is 9 months old, so perhaps I should merge a
later version in anyway.

My knowledge of how JFFS2 works internally is limited, so I would be
grateful for any advice.

Regards,
John Hall

             reply	other threads:[~2003-08-28  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28  9:50 John Hall [this message]
2003-08-28 10:23 ` Lost space on JFFS2 partition David Woodhouse
2003-08-28 10:28   ` John Hall
2003-08-28 11:27     ` David Woodhouse
2003-08-28 13:58       ` John Hall
2003-08-28 14:15         ` David Woodhouse
2003-08-28 14:25           ` John Hall
2003-08-28 14:46             ` David Woodhouse

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=6306.3f4dd070.667ee@irwin2.crw.uk.net \
    --to=john-news1@cambridgetechgroup.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