public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jeff Hane <jhane@mobilygen.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Flash_eraseall -j and cowardly refusing to mount
Date: Mon, 07 Jan 2008 10:39:19 -0800	[thread overview]
Message-ID: <1199731159.6533.10.camel@qu062.quarc.com> (raw)
In-Reply-To: <1199718040.27304.12.camel@pmac.infradead.org>


 But doesn't this only fix the case where you have contiguous 8 bytes to
write the cleanmarker?  flash_eraseall -j uses MTD_PLACE to write the
cleanmarker BUT jffs2 uses MTD_AUTO to read the cleanmarker.
 For example, if your oob area has byte 0 as the bad block indicator and
bytes 8-10 have ecc, there are only 7 consecutive free bytes.
flash_eraseall -j will only write 7 bytes so jffs2 will fail when
mounting the filesystem because it will read 8 bytes.  The 8th byte,
which will be byte 12, will still be FF.
  It seems there should be an ioctl that would allow one to read/write
the oob area using MTD_AUTO???

jeff

On Mon, 2008-01-07 at 15:00 +0000, David Woodhouse wrote:
> On Mon, 2008-01-07 at 12:16 +0000, Phillips, Owain wrote:
> > Hi linux-mtd@lists.infradead.org,
> > 
> > We just upgraded to mtd-utils-1.0.1 on our 2.6.23 target and I am
> > getting problems with flash_eraseall -j where the mount fails.
> 
> It ought to be fixed by this:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=09b3fba5
> 

      reply	other threads:[~2008-01-07 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 12:16 Flash_eraseall -j and cowardly refusing to mount Phillips, Owain
2008-01-07 12:40 ` Josh Boyer
2008-01-07 15:00 ` David Woodhouse
2008-01-07 18:39   ` Jeff Hane [this message]

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=1199731159.6533.10.camel@qu062.quarc.com \
    --to=jhane@mobilygen.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox