From: Matthieu CASTET <matthieu.castet@parrot.com>
To: linux-mtd@lists.infradead.org
Subject: jffs2 : duplicate node
Date: Mon, 21 May 2007 15:42:58 +0200 [thread overview]
Message-ID: <4651A1E2.60206@parrot.com> (raw)
Hi,
With jffs2 from 2.6.20 with summary enabled, I manage to get duplicate
inode node : there have the same (same header, crc, ...) [1]
Is that normal ?
I was thinking the version should be incremented each time the inode
node is modified.
Matthieu
[1] for a partition in 80000 a80000, I got
- fcf7c 248000 (len 208) is the same
- 248100 885074 (len 75) is the same
- 24817c 8850f0 (len 88) is the same
next reply other threads:[~2007-05-21 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:42 Matthieu CASTET [this message]
2007-05-21 15:53 ` jffs2 : duplicate node David Woodhouse
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=4651A1E2.60206@parrot.com \
--to=matthieu.castet@parrot.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;
as well as URLs for NNTP newsgroup(s).