From: David Woodhouse <dwmw2@infradead.org>
To: "Curtis, Allen" <Allen.Curtis@Thales-IFS.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: jffs2_scan_eraseblock() - errors
Date: Wed, 31 Jul 2002 00:42:14 +0100 [thread overview]
Message-ID: <16163.1028072534@redhat.com> (raw)
In-Reply-To: <FA06AA2C99BCD511951200005A99441001E3ECC3@irvexch1.sextantifs.com>
Allen.Curtis@Thales-IFS.com said:
> Questions then: 1. Does this node get reclaimed? I get this same
> message now with each reboot.
It'll get erased when that block gets garbage-collected.
> 2. It appears that the mount operation gets slower once this error
> condition occurs. Is this possible/expected?
Definitely not expected. I can't really see how it's possible. I'd say it's
probably a coincidence.
> 3. If the file-system becomes corrupted, what is the failure condition
> and how do you correct it? Test for it?
JFFS2 is purely log-structured. There are few ways in which the file system
as a whole can be declared to be 'corrupted'. The only real case I can
think of is when a directory with children appears to have no links from
the root inode, which is obviously a bug. In that case, we just delete the
offending directory and all its children. I suppose we should really
re-link it to /lost+found instead :)
--
dwmw2
next prev parent reply other threads:[~2002-07-30 23:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 23:30 jffs2_scan_eraseblock() - errors Curtis, Allen
2002-07-30 23:42 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 23:02 Curtis, Allen
2002-08-01 10:44 ` David Woodhouse
2002-07-31 1:15 Curtis, Allen
2002-07-31 3:07 ` David Woodhouse
2002-07-31 0:38 Curtis, Allen
2002-07-31 0:48 ` David Woodhouse
2002-07-30 23:59 Curtis, Allen
2002-07-31 0:15 ` David Woodhouse
2002-07-31 0:18 ` David Woodhouse
2002-07-30 18:11 Curtis, Allen
2002-07-30 22:21 ` David Woodhouse
2002-07-31 10:34 ` Jörn Engel
2002-07-31 11:45 ` David Woodhouse
2002-07-31 11:57 ` Jörn Engel
2002-07-31 11:59 ` David Woodhouse
2002-07-31 12:16 ` Jörn Engel
2002-07-31 12:17 ` David Woodhouse
2002-07-31 13:07 ` Jörn Engel
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=16163.1028072534@redhat.com \
--to=dwmw2@infradead.org \
--cc=Allen.Curtis@Thales-IFS.com \
--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.