From: Artem Bityutskiy <dedekind@infradead.org>
To: Elias <dilu666@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 tools
Date: Wed, 15 Nov 2006 17:01:46 +0200 [thread overview]
Message-ID: <1163602907.5597.4.camel@sauron> (raw)
In-Reply-To: <3aad55d90611150529v4ad67c51gf5ae36280c727005@mail.gmail.com>
On Wed, 2006-11-15 at 15:29 +0200, Elias wrote:
> I wonder if there are any tools for the jffs2 that can report various
> information about the file system and flash chip that it resides on,
> such as the structure of the dirty,clean and free blocks, the total
> data structure of the flash chip, as well as the physical allocation
> of data on the chip. Are there any?
Yeah, it would be nice to have such a debugging/analysis tool, but I am
not aware of any. There is JFFS2 dump which can dump the FS and you may
write a script which will provide you the needed information by means of
parsing its output. But beware the tool may be outdated. I am not sure
if it understands summary and xattr stuff which went to JFFS2 rather
recently.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2006-11-15 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 13:29 JFFS2 tools Elias
2006-11-15 15:01 ` Artem Bityutskiy [this message]
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=1163602907.5597.4.camel@sauron \
--to=dedekind@infradead.org \
--cc=dilu666@gmail.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.