From: Sander Smeenk <ssmeenk@freshdot.net>
To: linux-raid@vger.kernel.org
Subject: Re: Data corruption on software raid.
Date: Sun, 18 Mar 2007 23:00:05 +0100 [thread overview]
Message-ID: <20070318220005.GN6063@freshdot.net> (raw)
In-Reply-To: <45FD870C.3020403@tmr.com>
Quoting Bill Davidsen (davidsen@tmr.com):
> Here are several pertinent sections from Neils posts, topic
> "mismatch_cnt questions"
[..]
> Does any of that explain why I raise the possibility of the data
> changing as the file is written?
Yeah, that helps. But as i understand, these 'differences' are quickly
smoothed out. I tested the data after receiving it completely.
First thing i'll do is try to get a new disk for sdb, as SMART is dodgy
on the thing. Hopefully that will solve the problems, if it doesn't the
controller will be replaced.
I still think it's weird...
Regards,
Sander.
--
| 42.7 percent of all statistics are made up on the spot.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
next prev parent reply other threads:[~2007-03-18 22:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 13:16 Data corruption on software raid Sander Smeenk
2007-03-18 14:02 ` Justin Piszcz
2007-03-18 16:50 ` Bill Davidsen
2007-03-18 17:38 ` Sander Smeenk
[not found] ` <45FD870C.3020403@tmr.com>
2007-03-18 22:00 ` Sander Smeenk [this message]
2007-03-18 15:17 ` Wolfgang Denk
2007-03-18 17:09 ` Bill Davidsen
2007-03-18 22:16 ` Neil Brown
2007-03-18 22:19 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2008-04-07 23:43 Data corruption on software RAID Mikulas Patocka
2008-04-08 10:22 ` Helge Hafting
2008-04-08 11:14 ` Mikulas Patocka
2008-04-09 18:33 ` Bill Davidsen
2008-04-10 3:07 ` Mikulas Patocka
2008-04-10 14:21 ` Bill Davidsen
2008-04-11 2:55 ` Mikulas Patocka
2008-04-10 6:14 ` Mario 'BitKoenig' Holbe
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=20070318220005.GN6063@freshdot.net \
--to=ssmeenk@freshdot.net \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).