public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: crowe@psilongbeach.com, Kevin Liao <kevinliao@iei.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 warning message
Date: Fri, 27 Jun 2003 00:33:52 +0200	[thread overview]
Message-ID: <200306270033.52944.tglx@linutronix.de> (raw)
In-Reply-To: <3EFB3A35.3060104@psilongbeach.com>

On Thursday 26 June 2003 20:23, crowe@psilongbeach.com wrote:
> >>I had a mtd partition on NAND flash mounted as JFFS2. If the power was
> >> shutdown abnormally, after that each time when the system rebooted and
> >> tried to mount it again, I always saw a warning message "Empty flash at
> >> 0x00000a14 ends at 0x00000c00". Although I finally found that message
> >> was printed by jffs2_scan_eraseblock function in jffs2/scan.c, I still
> >> had no idea about what's really happened. Does anyone could explain the
> >> reason about that warning message or tell me what should I do to avoid
> >> the kernel's complaint? Thanks a lot.
>
> I see this warning message too, but the conditions are
> different (Type I flash, normal boot, ...).
> I haven't really dug into it, but I know that I've been creating
> the jffs2 file system image on a different machine (creating a target
> filesystem) on a i386 Linux box, then moving it over to my embedded arm
> target.  I just assumed that it was generated by having slightly different
> versions jffs2, or that I have debugging turned on.  Haven't had time to
> really look at it yet. So what I guess I'm saying is I see this too, and
> would also like to know how to get rid of it.
>
Nothing to be worried about. The page was not complete written to FLASH before 
power down, so the fs check on mount finds empty FLASH inside this page 
(0xff) and thinks the rest of the eraseblock is empty too. Then it finds at 
the beginning of the next page some new data and gives a message. That's just 
for information, as something is not as exspected. The fs can handle this and 
this is not a corruption or something like that, just a hint, which keeps you 
informed, that something happend.
If this bothers you, change the message level to KERN_DEBUG instead of 
KERN_WARNING. It will finally go away, when the offending eraseblock will be 
recycled sometimes.

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

      reply	other threads:[~2003-06-26 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 10:50 JFFS2 warning message Kevin Liao
2003-06-26  9:59 ` Kevin Liao
2003-06-26 18:23   ` crowe
2003-06-26 22:33     ` Thomas Gleixner [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=200306270033.52944.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=crowe@psilongbeach.com \
    --cc=kevinliao@iei.com.tw \
    --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