Dexter Filmore (Dexter.Filmore@xxxxxx) wrote on 21 April 2006 20:23: >Am Mittwoch, 19. April 2006 18:31 schrieb Shai: >> On 4/19/06, Dexter Filmore <Dexter.Filmore@xxxxxx> wrote: >> > Let's say a disk in an array starts yielding smart errors but is still >> > functional. >> > So instead of waiting for it to fail completely and start a sync and >> > stress the other disks, could I clone that disk to a fresh one, put the >> > array offline and replace the disk? >> >> Hi, >> >> Why can't you just mark that drive as failed, remove it and hotadd a >> new drive to replace the failed drive? > >Well, resync stresses the other disks a lot. If that can be avoided, I'd >rather do so. I'm not sure I understand what you want but you certainly can: stop the array dd warning disk => new one remove warning disk assemble the array again with the new disk The inconvenience is that you don't have the array during the copy. Perhaps you could also just change the first step to "put the array in read-only mode". This of course means your filesystem must be mounted ro but at least you can read from it. For this to work md must not make any changes to the disks, in particular it must not change the superblocks if a disk fails. I don't know if this is what happens. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
