linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Flexible storga: LVM setup on top of mdadm sets. Good idea or not?
Date: Tue, 21 Aug 2007 10:11:06 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0708211003560.11224-100000@bmsred.bmsi.com> (raw)
In-Reply-To: <20070821065251.GB16272@percy.comedia.it>

On Tue, 21 Aug 2007, Luca Berra wrote:

> >> False. md uses bitmaps to avoid this.
> >
> >Ok, I just tested this with Centos-5.0, kernel-2.6.18-8.1.8.el5.
> >I shutdown with md1 50% resynced, and when it boots, it starts over
> >at the beginning.  Maybe we are talking about different things, but
> >it is a major annoyance that it restarts the sync from the beginning
> >if it misses just one update (e.g. unexpected power failure or reboot).
> >
> did you add the bitmap to your md array?

I installed Centos5 from the CDs on raid1 devices.  I do see a bitmap
option in the map page for mdadm.  How do I check whether Centos5 install
neglected to activate it?  Is there any way to add it after the install?
(LVM is on md1 and root,swap are on LVM.)  If not, what would be the
install procedure to actually use a bitmap?  Note: special restrictions
on the boot partition are acceptable.  Special restrictions on the root
partition/LV are not.

# mdadm --examine /dev/hde3
/dev/hde3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 14c44605:1e3381da:9833dc4f:b4bdc3c0
  Creation Time : Mon Aug 20 15:13:47 2007
     Raid Level : raid1
    Device Size : 78059712 (74.44 GiB 79.93 GB)
     Array Size : 78059712 (74.44 GiB 79.93 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1

    Update Time : Tue Aug 21 10:06:36 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : bb50a9f9 - correct
         Events : 0.8


      Number   Major   Minor   RaidDevice State
this     0      33        3        0      active sync   /dev/hde3

   0     0      33        3        0      active sync   /dev/hde3
   1     1      34        3        1      active sync   /dev/hdg3

-- 
	      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.

      reply	other threads:[~2007-08-21 14:11 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
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 [this message]

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=Pine.LNX.4.44.0708211003560.11224-100000@bmsred.bmsi.com \
    --to=stuart@bmsi.com \
    --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).