<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<pre wrap="">Mike McCarty <a class="moz-txt-link-rfc2396E"
href="mailto:Mike.McCarty@sbcglobal.net"><Mike.McCarty@sbcglobal.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">David G. Miller wrote:
[snip]
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>I think the only data loss was during the period of time from when the
<span class="moz-txt-citetags">> </span>drive failed until I was able to pull the ribbon cable. Unfortunately,
<span class="moz-txt-citetags">> </span>the system was still trying to write to the dead drive.
</pre>
</blockquote>
<pre wrap=""><!---->
There should have been no data loss. If RAID works correctly, and you
have fewer failures than the array is designed to accept, there should
be no, emphasized no data loss.
[snip]
Mike</pre>
</blockquote>
I agree and that probably would have been the case if the drive had
cleanly died. The problem was it died a slow death. <br>
<br>
RAID kept trying to write data to the drive which is why I described
the system as being "wonky." It sort of worked but any I/O to/from the
array that included the bad drive took a long time due to the drive
errors. I finally decided that trying to let the system synchronize
would be worse than just "pulling the plug" so I forced a shutdown.
Luckily, it was a weekend and all that was lost were a few spams and
some cron status e-mails. I'd already checked that this was the case
when decided to force the reboot.<br>
<br>
Cheers,<br>
Dave<br>
<br>
</body>
</html>