Re: mdadm error when trying to replace a failed drive in RAID5 array
From: Ask Bjørn Hansen <hidden>
Date: 2008-01-21 10:38:01
From: Ask Bjørn Hansen <hidden>
Date: 2008-01-21 10:38:01
On Jan 20, 2008, at 1:21 PM, Steve Fairbairn wrote:
So the device I was trying to add was about 22 blocks too small. Taking Neils suggestion and looking at /proc/partitions showed this up incredibly quickly.
Always leave a little space in the end; it makes sure you don't run into that particular problem when you replace disks and the end of the disk is often significantly slower anyway. From before the write-intent bitmap stuff I have/had a habit of creating separate raids on relatively small partitions (joined together by LVM). I'd just pick a fixed size (on 500GB disks I'd use 90GB per partition for example) and create however many partitions would fit like that and leave the end for scratch space / experiments / whatever. - ask -- http://develooper.com/ - http://askask.com/