* Fwd: Majordomo results: Re: Majordomo results: . [not found] ` <e4ae6451002240048w7822735dx6143c07274fe99d5@mail.gmail.com> @ 2010-02-24 8:54 ` Felipe Alvarez 2010-02-24 9:07 ` Jon Hardcastle 0 siblings, 1 reply; 4+ messages in thread From: Felipe Alvarez @ 2010-02-24 8:54 UTC (permalink / raw) To: linux-raid Hi list. I've 4 X 320GB Sata disks in Raid 5 (mdadm - v2.6.7.1 - 15th October 2008). They all have a 0xFD raid autodetect parition, filling 100% of the drives. One drive failed, and I bought a 500GB disk (instead of 320GB). Should I just add /dev/sde as-is, allowing mdadm to automatically rebuild it as required? Or, should I partition it to exact same dimensions/size as the other disks, with part-type 0xFD? TIA Felipe end ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fwd: Majordomo results: Re: Majordomo results: . 2010-02-24 8:54 ` Fwd: Majordomo results: Re: Majordomo results: Felipe Alvarez @ 2010-02-24 9:07 ` Jon Hardcastle 2010-02-24 9:45 ` Felipe Alvarez 0 siblings, 1 reply; 4+ messages in thread From: Jon Hardcastle @ 2010-02-24 9:07 UTC (permalink / raw) To: linux-raid, Felipe Alvarez --- On Wed, 24/2/10, Felipe Alvarez <felipe.alvarez@gmail.com> wrote: > From: Felipe Alvarez <felipe.alvarez@gmail.com> > Subject: Fwd: Majordomo results: Re: Majordomo results: . > To: linux-raid@vger.kernel.org > Date: Wednesday, 24 February, 2010, 8:54 > Hi list. I've 4 X 320GB Sata disks in > Raid 5 (mdadm - v2.6.7.1 - 15th > October 2008). They all have a 0xFD raid autodetect > parition, filling > 100% of the drives. One drive failed, and I bought a 500GB > disk > (instead of 320GB). Should I just add /dev/sde as-is, > allowing mdadm > to automatically rebuild it as required? Or, should I > partition it to > exact same dimensions/size as the other disks, with > part-type 0xFD? > TIA > > Felipe > end > -- > 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 > AFAIK You can - after you have failed/removed etc the old drive. Create a new partition that is the same type - but not necessarily the identical size(i.e. fill the whole drive if you like but not smaller) and add it to the array. The beauty of that being that when all the drives have been retired/failed and the smallest partition size is now 500GB or whatever you can --grow=max and get that unused space. ----------------------- N: Jon Hardcastle E: Jon@eHardcastle.com 'Do not worry about tomorrow, for tomorrow will bring worries of its own.' *********** Please note, I am phasing out jd_hardcastle AT yahoo.com and replacing it with jon AT eHardcastle.com *********** ----------------------- -- 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fwd: Majordomo results: Re: Majordomo results: . 2010-02-24 9:07 ` Jon Hardcastle @ 2010-02-24 9:45 ` Felipe Alvarez 2010-02-24 9:50 ` Jon Hardcastle 0 siblings, 1 reply; 4+ messages in thread From: Felipe Alvarez @ 2010-02-24 9:45 UTC (permalink / raw) To: Jon; +Cc: linux-raid > The beauty of that being that when all the drives > have been retired/failed and the smallest partition > size is now 500GB or whatever you can > --grow=max and get that unused space. > Thanks. That's a good idea, because I would eventually like to make the array larger than it is as the drives get replaced, one at a time. Would the command be: $ mdadm --grow /dev/md0 --size=max DEVICE1 DEVICE2 DEVICE3 DEVICE4 Felipe ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fwd: Majordomo results: Re: Majordomo results: . 2010-02-24 9:45 ` Felipe Alvarez @ 2010-02-24 9:50 ` Jon Hardcastle 0 siblings, 0 replies; 4+ messages in thread From: Jon Hardcastle @ 2010-02-24 9:50 UTC (permalink / raw) To: Jon, Felipe Alvarez; +Cc: linux-raid --- On Wed, 24/2/10, Felipe Alvarez <felipe.alvarez@gmail.com> wrote: > From: Felipe Alvarez <felipe.alvarez@gmail.com> > Subject: Re: Fwd: Majordomo results: Re: Majordomo results: . > To: Jon@ehardcastle.com > Cc: linux-raid@vger.kernel.org > Date: Wednesday, 24 February, 2010, 9:45 > > The beauty of that being that > when all the drives > > have been retired/failed and the smallest partition > > size is now 500GB or whatever you can > > --grow=max and get that unused space. > > > Thanks. That's a good idea, because I would eventually like > to make > the array larger than it is as the drives get replaced, one > at a time. > Would the command be: > $ mdadm --grow /dev/md0 --size=max DEVICE1 DEVICE2 DEVICE3 > DEVICE4 > > Felipe > -- Think it is simply mdadm --grow /dev/md0 --size=max But speaking from experience you'll likely run out of space before the bitter pill of retiring the drives/being unlucky enough for them to fail happens. You'll be adding new drives before you know it! And then... you'll probably want to consider RAID6 once you go over ~1TB per drive. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-02-24 9:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <S1753924Ab0BXIaN/20100224083013Z+196@vger.kernel.org>
[not found] ` <e4ae6451002240032q17390a5ci4baa86cc7be8270e@mail.gmail.com>
[not found] ` <e4ae6451002240048w7822735dx6143c07274fe99d5@mail.gmail.com>
2010-02-24 8:54 ` Fwd: Majordomo results: Re: Majordomo results: Felipe Alvarez
2010-02-24 9:07 ` Jon Hardcastle
2010-02-24 9:45 ` Felipe Alvarez
2010-02-24 9:50 ` Jon Hardcastle
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox