From: David Woodhouse <dwmw2@infradead.org>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: MTD <linux-mtd@lists.infradead.org>
Subject: Re: Data CRC failed on node at ...
Date: Thu, 30 Jan 2003 19:34:53 +0000 [thread overview]
Message-ID: <14124.1043955293@passion.cambridge.redhat.com> (raw)
In-Reply-To: <3E395E76.5030401@imc-berlin.de>
steven.scholz@imc-berlin.de said:
> What can I do now?
Ignore it.
> Is there something like a repair tool?
Not at the moment, no.
> Or can I at least find out which file is corrupted?
Nothing's corrupted. It's probably because the machine was powered off or
rebooted while it was busy garbage-collecting. As it writes out new
replacement nodes before the old ones are marked obsolete, if you interrupt
it, it means that the original node will have remained intact on the flash
-- only the new node which was _going_ to replace it is broken, and that's
part of what the CRC check is there for.
It'll go away in time when the block in which the offending node resides is
garbage collected.
--
dwmw2
prev parent reply other threads:[~2003-01-30 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 17:18 Data CRC failed on node at Steven Scholz
2003-01-30 19:34 ` David Woodhouse [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=14124.1043955293@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=steven.scholz@imc-berlin.de \
/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