On Mon, 23 Jul 2007, Luca Berra wrote:
> On Sun, Jul 22, 2007 at 02:57:33PM -0400, Stuart D. Gathman wrote:
> >The main drawback to md raid1 is that it always resynchronizes
> >the *entire* partition when a disk goes offline temporarily. I also
> False. md uses bitmaps to avoid this.
I am using md on dozens of systems up through Centos-5. If there are any
bitmaps, they don't work. Or maybe they are a new feature not in kernel
2.6.18. The only change I've noticed since RH7.3 is that sync speed is no
longer limited to 10K. Or maybe I'm not looking at the right thing.
When replacing a disk, a full resync is required anyway - so no problem.
Where it is a problem is when there is an abnormal system shutdown,
so that md devices are not closed properly. The system boots immediately,
but performance is slow until the mirror have been resynced. This can
take hours. And the system is vulnerable to single disk failure in the source
drive for those hours.
How would I see these bitmaps in action?
BTW, to upgrade a 7.2 system to Centos5, I plan to install on a disk
with matching partition sizes and replace boot drive. Is there any
chance that md raid1 will sync from the old system overtop the new?
(Because the new wouild have lower sequence numbers?) Or is there some
kind of UUID in the raid superblock to prevent this? (Of course I plan
to change partition types away from RAID Auto just to be safe...)
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
