All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 an nodes checking
Date: Tue, 28 Sep 2004 17:37:23 +0400	[thread overview]
Message-ID: <41596913.6080207@yandex.ru> (raw)
In-Reply-To: <1096377761.30942.58.camel@hades.cambridge.redhat.com>

David Woodhouse wrote:
> On Tue, 2004-09-28 at 17:17 +0400, Artem B. Bityuckiy wrote:
> 
>>Ok. But what if we check only last node (with the highest version) and 
>>if it is OK, don't check anything more? If it is bad, check previous, 
>>and so on. It seems for me, these checks are enough. We cover the 
>>situation with unexpected power losses.
> 
> 
> There's no reason to presume that the only node with broken CRC will be
> the _latest_ node, especially on NAND flash.
> 
If this isn't last node, the reason is media errors. And it isn't JFFS2 
deal to restore data. Moreover, this isn't guarantied in the current 
implementation - the previous node(s) may have been already Garbage 
Collected.

Another possibility is to teach the GC not to delete obsolete nodes for 
not yet checked inodes. And the fall-back procedure must be done if the 
bad node is read after the file was opened but its data wasn't checked 
(iput() and iget() again).

Comments?

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

  reply	other threads:[~2004-09-28 13:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 12:29 JFFS2 an nodes checking Artem B. Bityuckiy
2004-09-28 12:37 ` David Woodhouse
2004-09-28 13:17   ` Artem B. Bityuckiy
2004-09-28 13:22     ` David Woodhouse
2004-09-28 13:37       ` Artem B. Bityuckiy [this message]
2004-09-28 13:45         ` David Woodhouse
2004-09-28 13:57           ` Artem B. Bityuckiy
2004-09-28 14:04             ` David Woodhouse
2004-09-28 14:26               ` Artem B. Bityuckiy
2004-09-28 14:37                 ` David Woodhouse
2004-09-28 14:58                   ` Artem B. Bityuckiy
2004-09-28 15:04                     ` David Woodhouse
2004-09-28 14:31               ` Josh Boyer
2004-09-28 14:47                 ` Artem B. Bityuckiy
2004-09-28 14:58                   ` David Woodhouse
2004-09-28 16:48                     ` Artem B. Bityuckiy
2004-09-28 16:57                       ` Josh Boyer
2004-09-28 16:58                       ` David Woodhouse
2004-09-28 17:15                         ` Artem B. Bityuckiy
2004-09-28 18:24                         ` Josh Boyer

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=41596913.6080207@yandex.ru \
    --to=abityuckiy@yandex.ru \
    --cc=dwmw2@infradead.org \
    --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.