From: Semih Hazar <semih.hazar@indefia.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Strange JFFS2 Cleanmarker on NAND
Date: Sat, 28 Apr 2007 15:57:59 +0300 [thread overview]
Message-ID: <463344D7.2060503@indefia.com> (raw)
In-Reply-To: <46322E19.7020409@indefia.com>
Semih Hazar wrote:
> I re-run the above step (without -j and with -j) and now cleanmarkers
> are ok and I can mount it.
>
Well It seems that this behavior is totally random. I did these steps
lots of times, and sometimes the cleanmarker is written as:
ff ff 19 85 20 05 00 00 00 18 65 fa fd 45 00 00
00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
and sometimes written as:
ff ff 19 85 20 03 00 00 00 08 ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Does the first one have any meaning or is it some messed up data ?
prev parent reply other threads:[~2007-04-28 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 17:08 Strange JFFS2 Cleanmarker on NAND Semih Hazar
2007-04-28 12:57 ` Semih Hazar [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=463344D7.2060503@indefia.com \
--to=semih.hazar@indefia.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