From: michael <trimarchi@gandalf.sssup.it>
To: linux-mtd@lists.infradead.org
Subject: jffs2 failing after reboot on dataflash. 2.6.24
Date: Sat, 16 Feb 2008 14:53:11 +0100 [thread overview]
Message-ID: <47B6EAC7.7070208@gandalf.sssup.it> (raw)
Hi,
I use a dataflash for jffs2. The filesystem seems to work correctly but
at the first reboot
I have some different and some file corruption. This is the different of
two dump:
9475c9475,9489
< Empty space: 18268, dirty space: 0
---
> Empty space found from 0x00444cec to 0x00444de0
> Inode node at 0x00444de0, totlen 0x0000041b, #ino
681, version 67, isize 66031, csize 983, dsize 2701,
offset 49632
> Wrong bitmask at 0x004451fc, 0x0000
> Empty space found from 0x00445200 to 0x00504f00
> Inode node at 0x00504f00, totlen 0x00000590, #ino
681, version 68, isize 66031, csize 1356, dsize 3168,
offset 49632
> Inode node at 0x00505490, totlen 0x00000044, #ino
681, version 69, isize 66031, csize 0, dsize 1056,
offset 52800
> Inode node at 0x005054d4, totlen 0x00000531, #ino
681, version 70, isize 66031, csize 1261, dsize 3168,
offset 53856
> Inode node at 0x00505a08, totlen 0x00000044, #ino
681, version 71, isize 66031, csize 0, dsize 1056,
offset 57024
> Inode node at 0x00505a4c, totlen 0x00000641, #ino
681, version 72, isize 66031, csize 1533, dsize 3168,
offset 58080
> Inode node at 0x00506090, totlen 0x00000044, #ino
681, version 73, isize 66031, csize 0, dsize 1056,
offset 61248
> Inode node at 0x005060d4, totlen 0x0000063b, #ino
681, version 74, isize 66031, csize 1527, dsize 3168,
offset 62304
> Inode node at 0x00506710, totlen 0x00000044, #ino
681, version 75, isize 66031, csize 0, dsize 559,
offset 65472
> Dirent node at 0x00506754, totlen 0x00000032, #pino
673, version 680, #ino 682, nsize 10, name pulldom.py
> Padding node at 0x00506788, totlen 0x00000038
> Empty space: 2933884, dirty space: 4
The file #ino 681 is corrupted.
The first is the original images creates with mkfs.jffs2, the second one
is the filesystem after the first reboot. I don't understand
why there new inode created, that invalidate my image.
Regards Michael
reply other threads:[~2008-02-16 13:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47B6EAC7.7070208@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--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