From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Dmitry Bazhenov <atrey@emcraft.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 node versioning problem?
Date: Wed, 03 May 2006 16:02:22 +0400 [thread overview]
Message-ID: <44589BCE.2060402@yandex.ru> (raw)
In-Reply-To: <200605031556.37660.atrey@emcraft.com>
Dmitry Bazhenov wrote:
> Hello everybody!
>
> I was just thinking about hypothetical situation with JFFS2 wich possibly
> could be met in the reality. What happens when the highest node version of a
> certain inode exceeds the maximum value?
>
> I think this can be a point where the inode can be broken. If there are two
> data nodes which have overlapped regions and more recent node has a lesser
> value then the other node has, then, when the partition is dismounted and
> mounted again the more recent inode is treated as an older one and could be
> obsoleted. Even if it is not obsoleted, its data become superseeded by data
> from the least recent node as the last one has a higher version number.
>
Can it happen with a real-life flash device? If it can, we have to
switch to 64-bit versions.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2006-05-03 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 11:56 JFFS2 node versioning problem? Dmitry Bazhenov
2006-05-03 12:02 ` Artem B. Bityutskiy [this message]
2006-05-03 14:28 ` Dmitry Bazhenov
2006-05-03 14:35 ` Dmitry Bazhenov
2006-05-03 14:42 ` Artem B. Bityutskiy
2006-05-03 14:40 ` Artem B. Bityutskiy
2006-05-03 15:07 ` Dmitry Bazhenov
2006-05-03 15:07 ` Josh Boyer
2006-05-03 15:11 ` Josh Boyer
2006-05-03 15:21 ` Jörn Engel
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=44589BCE.2060402@yandex.ru \
--to=dedekind@yandex.ru \
--cc=atrey@emcraft.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.