From: Vipin Malik <vipin.malik@daniel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Frederic Giasson <fgiasson@mediatrix.com>,
linux-mtd@lists.infradead.org, jffs-dev@axis.com,
Jean-Denis Boyer <jdboyer@mediatrix.com>
Subject: Re: JFFS2 Stability problem!
Date: Mon, 16 Jul 2001 09:37:26 -0500 [thread overview]
Message-ID: <3B52FC26.840B1832@daniel.com> (raw)
In-Reply-To: 21355.995292592@redhat.com
David Woodhouse wrote:
> fgiasson@mediatrix.com said:
> > I found a stability problem that looks like a flash space leak while
> > running intense test case with JFFS2.
>
> Definitely looks like a leak. Does the space come back after an unmount and
> remount?
[root@elan /root]# rm -rf /mnt/jffs2/*
[root@elan /root]# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock1 8192 2544 5648 31% /mnt/jffs2
[root@elan /root]# umount /mnt/jffs2/
[root@elan /root]#
[root@elan /root]# mount -t jffs2 /dev/mtdblock1 /mnt/jffs2/
[root@elan /root]#
[root@elan /root]# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock1 8192 1284 6908 16% /mnt/jffs2
[root@elan /root]#
Hence Yes!
Vipin
P.S. I also got some strange (debug type) messages from JFFS2 on the terminal I
was running the program at, but NOT on the serial console (why?)
I sent those to Frederic. I don't have access to those here, but maybe Frederic
can forward them to you. It may help decipher what is going on.
next prev parent reply other threads:[~2001-07-16 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 13:54 JFFS2 Stability problem! Frederic Giasson
2001-07-16 14:09 ` David Woodhouse
2001-07-16 14:37 ` Vipin Malik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 14:34 Frederic Giasson
2001-07-16 14:42 ` David Woodhouse
2001-07-16 14:47 ` Vipin Malik
2001-07-17 7:11 ` David Woodhouse
2001-07-17 17:00 ` Doron Sandroy
2001-07-17 12:20 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=3B52FC26.840B1832@daniel.com \
--to=vipin.malik@daniel.com \
--cc=dwmw2@infradead.org \
--cc=fgiasson@mediatrix.com \
--cc=jdboyer@mediatrix.com \
--cc=jffs-dev@axis.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 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.