From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: Re: CRC failed on node ....
Date: Tue, 20 Sep 2005 20:43:27 -0500 [thread overview]
Message-ID: <00ba01c5be4d$dcbe5eb0$0260a8c0@p4p800> (raw)
In-Reply-To: A61771BC4AE2DD41B460E8D73082E6E307AA30FF@olympus.hekimian.com
So, should the garbage collection eventually fix it by itself?
> In the power fail testing I have done, I did not see any files corrupted,
> other than the actual file data that was being actively written at the time
> of the power fail. I did see the same type of message and I assumed that
> that it was leftover junk that would get garbage collected later. I could
> not seem to force it to go away.
>
> Vern Sauder
next parent reply other threads:[~2005-09-21 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A61771BC4AE2DD41B460E8D73082E6E307AA30FF@olympus.hekimian.com>
2005-09-21 1:43 ` Brian T [this message]
2005-09-20 22:21 CRC failed on node Brian T
2005-09-21 13:01 ` Artem B. Bityutskiy
2005-09-21 15:29 ` Brian T
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='00ba01c5be4d$dcbe5eb0$0260a8c0@p4p800' \
--to=btuch@usa.net \
--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