public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Stefan Stürke" <sst@pandatel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.jffs2
Date: Fri, 13 Aug 2004 15:54:19 +0100	[thread overview]
Message-ID: <1092408859.14552.3.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <loom.20040813T164242-792@post.gmane.org>

On Fri, 2004-08-13 at 14:45 +0000, Stefan Stürke wrote:
> jffs2_scan_empty(): Empty block at 0x0000fffc ends at 0x00010000 (with
> 0x1985e002)! Marking dirty
> 
> Is it save to ignore these errors?

Yes. It's observing that there's padding between 0xfffc and 0x10000.
This is done because nodes aren't allowed to cross and eraseblock
boundary, and the image was created for 64KiB eraseblocks. It's harmless
though.

-- 
dwmw2

  reply	other threads:[~2004-08-13 14:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 12:02 mkfs.jffs2 Stefan Stürke
2004-08-13 12:31 ` mkfs.jffs2 David Woodhouse
2004-08-13 14:45   ` mkfs.jffs2 Stefan Stürke
2004-08-13 14:54     ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-07  9:32 mk.jffs2 Munira Ahmed
2005-06-07 11:10 ` mkfs.jffs2 Jarkko Lavinen
2005-02-21 13:28 mkfs.jffs2 Narinder Kumar
2005-02-21 13:58 ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-21 14:18   ` mkfs.jffs2 Narinder Kumar
2005-02-21 15:21     ` mkfs.jffs2 Andrew Victor
2005-02-24  8:11       ` mkfs.jffs2 Narinder Kumar
2005-02-24 13:20         ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-24 13:41           ` mkfs.jffs2 Narinder Kumar
2005-02-21 14:05 ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-21 14:25   ` mkfs.jffs2 Narinder Kumar
2005-02-21 14:35     ` mkfs.jffs2 Artem B. Bityuckiy
2005-02-22  5:03       ` mkfs.jffs2 Narinder Kumar
2002-09-05 12:35 mkfs.jffs2 Kenneth Johansson
2001-08-22 21:00 mkfs.jffs2 Ashok M Padmanaban
2001-08-22 15:44 ` mkfs.jffs2 Russ Dill

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=1092408859.14552.3.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sst@pandatel.com \
    /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