From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: linux-mtd@lists.infradead.org
Subject: Re: Unable to recover from CRC failiure
Date: Wed, 27 Mar 2002 13:37:26 +0000 [thread overview]
Message-ID: <18619.1017236246@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLKELLFCAA.joakim.tjernlund@lumentis.se>
joakim.tjernlund@lumentis.se said:
> >>???; c007fbc8 <jffs2_do_unlink+2e0/338> <=====
> Trace; c007fb0c <jffs2_do_unlink+224/338>
Now fixed, I think.
> But why can't JFFS2 resolve this itself? Should it not just "delete"
> the bad nodes?
Possibly, yes.
--
dwmw2
next prev parent reply other threads:[~2002-03-27 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 21:23 CVS tags? Andrew Dixon
2002-03-23 10:22 ` Jörn Engel
2002-03-25 14:48 ` Andrew Dixon
2002-03-25 15:37 ` Joakim Tjernlund
2002-03-25 15:43 ` David Woodhouse
2002-03-27 10:46 ` Unable to recover from CRC failiure Joakim Tjernlund
2002-03-27 10:54 ` David Woodhouse
2002-03-27 12:22 ` Joakim Tjernlund
2002-03-27 12:29 ` David Woodhouse
2002-03-27 13:14 ` Joakim Tjernlund
2002-03-27 13:37 ` David Woodhouse [this message]
2002-03-27 17:00 ` unsubscribe Roy Sherrill
2002-03-25 17:29 ` CVS tags? Jörn Engel
2002-03-25 15:54 ` David Woodhouse
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=18619.1017236246@redhat.com \
--to=dwmw2@infradead.org \
--cc=joakim.tjernlund@lumentis.se \
--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