<div dir="ltr"><div>I don't care what you do, if a program operating in userspace can kill a disk, I would call that a hardware problem. Even if the hardware didn't want to claim the problem then the filesystem should be responsible for it.<br>
<br></div>My honest guess is that you were just hit with a string of bad luck. Were the drives that failed the same make/model/manufacture date?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 9:58 PM, Daira Hopwood <span dir="ltr"><<a href="mailto:daira@jacaranda.org" target="_blank">daira@jacaranda.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 15/04/14 01:34, Greg Troxel wrote:<br>
><br>
> I run tahoe servers on 4 systems in a private grid. The grid is not<br>
> used much, but I run deep-check --repair --add-lease every week or so,<br>
> when I remember. The nodes all have lease expiration turned on, but are<br>
> quite unfull. All are running NetBSD, some -5, some -6. I do not have<br>
> these filesystems mounted noatime.<br>
><br>
> 3 of these nodes are physical machines, with 3 kinds of disks. All have<br>
> turned up bad blocks. The 4th is a Xen domU; the dom0 is RAID-1. One<br>
> of the dom0's disks also had some bad blocks. This is a notable<br>
> cluster; disk failures are otherwise relatively rare.<br>
><br>
> So I really wonder if the lease checking code, or something, is churning<br>
> the disk.<br>
><br>
> Has anyone else seen this?<br>
<br>
</div></div>'tahoe deep-check --repair --add-lease' will write to the header of<br>
every share.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Daira Hopwood ⚥<br>
<br>
</font></span><br>_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br>
<a href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
<br></blockquote></div><br></div>