Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Guy Watkins" <guy@watkins-home.com>
To: 'Tom Carlson' <twigathy@gmail.com>, "'Majed B.'" <majedb@gmail.com>
Cc: 'Tim Bostrom' <tbostrom@gmail.com>,
	'linux-raid' <linux-raid@vger.kernel.org>
Subject: RE: RAID 5 array recovery - two drives errors in external enclosure
Date: Fri, 18 Sep 2009 21:35:33 -0400	[thread overview]
Message-ID: <AFD5FB84146A49B186DAB822C95DE16D@m5> (raw)
In-Reply-To: <1f0f1a960909181817s6ad0a3f3l386a478603e9fde8@mail.gmail.com>

If you are starting over, maybe you should use RAID6?

} -----Original Message-----
} From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
} owner@vger.kernel.org] On Behalf Of Tom Carlson
} Sent: Friday, September 18, 2009 9:18 PM
} To: Majed B.
} Cc: Tim Bostrom; linux-raid
} Subject: Re: RAID 5 array recovery - two drives errors in external
} enclosure
} 
} 2009/9/19 Majed B. <majedb@gmail.com>:
} > If you're going to take all your data out, I would suggest you do a
} > clean start and zero out all the disks to force the remapping of bad
} > sectors, then run smartctl -t offline on all disks and after it's done
} > (it will take A LONG time), create your filesystem on an array and put
} > back your data.
} 
} I'd recommend running the badblocks program on each device to be put
} in the array too, just to be certain that none of your disks are going
} to go horribly flakey on assembly and build... I'm not sure if the
} offline smart test does a full scan like badblocks would.
} 
} T
} --
} To unsubscribe from this list: send the line "unsubscribe linux-raid" in
} the body of a message to majordomo@vger.kernel.org
} More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2009-09-19  1:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 20:42 RAID 5 array recovery - two drives errors in external enclosure Tim Bostrom
2009-09-17 21:22 ` Robin Hill
2009-09-17 21:35   ` Majed B.
2009-09-17 21:51     ` Tim Bostrom
2009-09-17 22:11       ` Majed B.
2009-09-17 22:23         ` Tim Bostrom
2009-09-18  7:58         ` Robin Hill
2009-09-17 23:11   ` Tim Bostrom
2009-09-17 23:28     ` Majed B.
2009-09-17 23:54       ` Tim Bostrom
2009-09-18  1:31         ` Guy Watkins
2009-09-18  3:50           ` Tim Bostrom
2009-09-18  4:19           ` Tim Bostrom
2009-09-18  8:07             ` Robin Hill
2009-09-18 15:27               ` Tim Bostrom
2009-09-18 15:41                 ` Robin Hill
     [not found]                 ` <6b696870909180910q67d8166ay7796321b8cd35809@mail.gmail.com>
     [not found]                   ` <2267211f0909180912p745e4ea0idb5659cb54a6adce@mail.gmail.com>
     [not found]                     ` <6b696870909180923m35f29fa2l857b6f6402eb20be@mail.gmail.com>
     [not found]                       ` <2267211f0909181041o29d6f5eft1e260696c6ab9c57@mail.gmail.com>
     [not found]                         ` <6b696870909181317x777e3c5dsdcf0e7709f9c4979@mail.gmail.com>
2009-09-18 23:30                           ` Tim Bostrom
2009-09-18 23:37                             ` Majed B.
2009-09-19  1:17                               ` Tom Carlson
2009-09-19  1:35                                 ` Guy Watkins [this message]
2009-09-21  4:40                                   ` Tim Bostrom
2009-09-21  4:59                                     ` Guy Watkins
2009-09-21  7:05                                     ` Majed B.

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=AFD5FB84146A49B186DAB822C95DE16D@m5 \
    --to=guy@watkins-home.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=majedb@gmail.com \
    --cc=tbostrom@gmail.com \
    --cc=twigathy@gmail.com \
    /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