From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Flexible storga: LVM setup on top of mdadm sets. Good idea or not?
Date: Tue, 24 Jul 2007 10:48:20 +0200 [thread overview]
Message-ID: <20070724084820.GA26108@percy.comedia.it> (raw)
In-Reply-To: <Pine.LNX.4.44.0707231231340.4791-100000@bmsred.bmsi.com>
On Mon, Jul 23, 2007 at 12:43:17PM -0400, Stuart D. Gathman wrote:
>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.
man mdadm
Bitmaps are a feature of md since mdadm-2.0 (kernel 2.6.13 or 2.6.14)
...
>How would I see these bitmaps in action?
man mdadm
but basically
mdadm -G /dev/md?? -b internal
>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...)
unfortunately redhat insisted for a long time on using the in-kernel md
auto-detect, which iirc just ignores md uuid. i think this is still true
in redhat5.
changing partition type will prevent this
creating the new raid with a different minor will prevent this
or change the minor of the old raid.
... but we're getting offtopic.
if you have further questions post them on linux-raid.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2007-07-24 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 16:50 [linux-lvm] Flexible storga: LVM setup on top of mdadm sets. Good idea or not? js
2007-07-22 18:57 ` Stuart D. Gathman
2007-07-23 7:23 ` Luca Berra
2007-07-23 16:43 ` Stuart D. Gathman
2007-07-24 8:48 ` Luca Berra [this message]
2007-07-24 1:44 ` Stuart D. Gathman
2007-07-24 9:13 ` Bryn M. Reeves
2007-08-21 0:33 ` Stuart D. Gathman
2007-08-21 6:52 ` Luca Berra
2007-08-21 14:11 ` Stuart D. Gathman
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=20070724084820.GA26108@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).