From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 with sync burst mode
Date: Thu, 10 Mar 2005 17:48:49 +0100 [thread overview]
Message-ID: <20050310164848.GB7018@synertronixx3> (raw)
In-Reply-To: <Pine.LNX.4.58.0503101621110.5506@phoenix.infradead.org>
Am 2005-03-10 16:21 +0000 schrieb Artem B. Bityuckiy:
> > 00435660: 0000 0000 0000 0000 b882 2ec7 8519 01e0 ................
> > 00435670: 3c00 0000 c001 e8b0 fb00 0000 1300 0000 <...............
> ^
> node length
> > 00435680: 0d01 0000 9400 0000 1408 0000 55ff 2d7c ............U.-|
> ^
> name length
> > 00435690: a9c7 cf9f 6c69 6270 7468 7265 6164 2d30 ....libpthread-0
> ^^^^ ^^^^
> Name CRC
> > 004356a0: 2e39 2e32 362e 736f 8519 02c0 a906 0000 .9.26.so........
> > 004356b0: 4a1e 6fb8 0d01 0000 0200 0000 a481 0000 J.o.............
> > 004356c0: 0000 0000 0010 0000 9400 0000 9400 0000 ................
> Where has this dump come from?
My initial Mail:
I did "cat /dev/mtdblock3 > file1" into nfs-root (as a side note, I did
the same again with dd bs=1024k:
konsti at synertronixx3:/usr/src/debian_arm/ > md5sum ddmtdblock3
e871d71c52d93c1cafb4a8f4ff47a741 ddmtdblock3
konsti at synertronixx3:/usr/src/debian_arm/ > md5sum mtdblock3
e871d71c52d93c1cafb4a8f4ff47a741 mtdblock3
).
This is emacs in hexl-mode on these files:
> This dump looks good:
And this dump is read from the same system right after umounting.
> * the length of node is 0x3c
> * the length of the name is 0x14
> * the name CRC - don't know, didn't calculate.
>
> Looks like JFFS2 really reads messed data from flash and I think this
> isn't JFFS2'd failure.
> I'd suggest to hack the write function and after each write read the data
> that has just been written again and check it has is the same as the
> original data. This check might be done either on MTD layer or on JFFS2
> layer.
But the error seems quite systematic so I suspect software. But of
course, still my setup my be broken and jffs2 triggers something. I have
no clue what though.
I will look into the code and see if I find the "write" to read
afterwards... :/
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2005-03-10 16:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 13:14 jffs2 with sync burst mode Konstantin Kletschke
2005-03-10 13:15 ` Artem B. Bityuckiy
2005-03-10 15:22 ` Konstantin Kletschke
2005-03-10 15:54 ` Artem B. Bityuckiy
2005-03-10 16:40 ` Konstantin Kletschke
2005-03-10 19:25 ` Steve Wahl
2005-03-10 23:24 ` Konstantin Kletschke
2005-03-10 15:46 ` Konstantin Kletschke
2005-03-10 16:21 ` Artem B. Bityuckiy
2005-03-10 16:48 ` Konstantin Kletschke [this message]
2005-03-10 17:08 ` Artem B. Bityuckiy
[not found] ` <JPEALJAFNGDDLOPNDIEECEJFDBAA.joakim.tjernlund@lumentis.se>
2005-03-10 23:18 ` Konstantin Kletschke
[not found] ` <BCEFJBPJCGFCNMMMIDBHEEPKCKAA.Joakim.Tjernlund@lumentis.se>
2005-03-11 0:03 ` Konstantin Kletschke
2005-03-10 17:02 ` Konstantin Kletschke
2005-03-10 17:17 ` Artem B. Bityuckiy
2005-03-10 18:27 ` Konstantin Kletschke
2005-03-10 18:53 ` Konstantin Kletschke
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 10:44 Konstantin Kletschke
2005-03-11 11:15 ` Artem B. Bityuckiy
2005-03-11 11:27 ` Konstantin Kletschke
2005-03-11 11:59 ` Artem B. Bityuckiy
2005-03-11 11:57 ` Konstantin Kletschke
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=20050310164848.GB7018@synertronixx3 \
--to=lists@ku-gbr.de \
--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.