public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Sébastien Côté" <scote1@Matrox.COM>
To: Simon Munton <Simon.Munton@m4data.co.uk>
Cc: "JFFS (E-mail)" <jffs-dev@axis.com>,
	"MTD (E-mail)" <mtd@infradead.org>,
	Finn Hakansson <finn@axis.com>
Subject: Re: intrep.c update to handle gaps in the middle of the log.
Date: Thu, 27 Jul 2000 10:13:19 -0400	[thread overview]
Message-ID: <3980437F.E174E66F@matrox.com> (raw)
In-Reply-To: 00B4D286538DD311BC6E005004E9EFC729B4A6@M4EXCH

Simon Munton wrote:
> >
> > If we have :
> >
> > >         0x000000 - 0x2b0000:    valid nodes
> > >         0x2b0000 - 0x2b7000:    all 0xff    The error occured here
> > >         0x2b7000 - 0x2c0000:    all zero      We set this
> > space as dirty
> > >       0x2c0000 - 0x2c8cff:    valid nodes
> > >         0x2c8d00 - 0x75ffff:    all 0xff
> > >         0x760000 - 0x76049f:    all zero
> > >         0x7604a0 - 0x7dffff:    valid nodes
> >
> In this case, how does JFFS decide where the end of the log is? Is it at the
> start of the first free space, or the second? My gut reaction would be to
> set all but the largest of the free spaces to be dirty.

That seems correct to me, if you also set dirty the free space at the
beginning of the corrupted sector.

-- 
Sébastien Côté


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-07-27 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-27 13:57 intrep.c update to handle gaps in the middle of the log Simon Munton
2000-07-27 14:13 ` Sébastien Côté [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-27 12:29 Simon Munton
2000-07-27 13:27 ` Sébastien Côté

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=3980437F.E174E66F@matrox.com \
    --to=scote1@matrox.com \
    --cc=Simon.Munton@m4data.co.uk \
    --cc=finn@axis.com \
    --cc=jffs-dev@axis.com \
    --cc=mtd@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