On Wed, Oct 22, 2008 at 9:52 AM, Stephan von Krawczynski<skraw@xxxxxxxxxx> wrote:> On Wed, 22 Oct 2008 09:15:45 -0400> Chris Mason <chris.mason@xxxxxxxxxx> wrote:>>> On Wed, 2008-10-22 at 14:27 +0200, Stephan von Krawczynski wrote:>> > On Tue, 21 Oct 2008 13:31:37 -0400>> > Ric Wheeler <ricwheeler@xxxxxxxxx> wrote:>> >>> > > [...]>> > > If you have remapped a big chunk of the sectors (say more than 10%), you>> > > should grab the data off the disk asap and replace it. Worry less about>> > > errors during read, writes indicate more serious errors.>> >>> > Ok, now for the bad news: money is invented.>> > If you replace a disk before real failure you won't get replacement from the>> > manufacturer. That may sound irrelevant to someone handling 5 disks, but is>> > significant if handling 500 or more. The replacement rate is indeed much>> > higher than people think from their home pcs.>>>> Hardware vendors already do replace disks based on policies defined by>> their own array hardware. These are already predictive.>> Lets agree that the market for drives, arrays and related stuff is big and> contains just about any example one needs for arguing :-)> Nevertheless we probably agree that if john doe meets big-player and tries to> warranty-replace a non-dead drive he will have troubles.>If John Doe is using redundant storage in the first place, he justneeds an emergency disk that can be swapped-in for a failing disk, andthen stress-test the failing disk to death, get it replaced bymanufacturer, and the replacement becomes the next standby/emergencydisk. Though it would be nice to have a tool that would provide enoughinformation to make a warranty claim -- does btrfs keep enoughinformation for such a tool to be written? Thanks, -- miʃel salim • http://hircus.jaiku.com/IUCS • msalim@xxxxxxxxxxxxxxxxxxxx • salimma@xxxxxxxxxxxxxxxxxxxxxxxxx • hircus@xxxxxxxxxxxx��.n��������+%������w��{.n�����{����n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�m
