Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: lrhorer@satx.rr.com
Cc: 'Neil Brown' <neilb@suse.de>,
	'Carlos Carvalho' <carlos@fisica.ufpr.br>,
	linux-raid@vger.kernel.org
Subject: Re: Write intent bitmaps
Date: Mon, 29 Jun 2009 12:01:13 +0200	[thread overview]
Message-ID: <87my7r1hqu.fsf@frosties.localdomain> (raw)
In-Reply-To: <20090628181428746.EXYX19511@cdptpa-omta03.mail.rr.com> (Leslie Rhorer's message of "Sun, 28 Jun 2009 13:14:23 -0500")

"Leslie Rhorer" <lrhorer@satx.rr.com> writes:

>> >  >5. What happens if the bitmap is lost or the external drive fills up?
>> >
>> > No idea.
>> 
>> If the bitmap is lost, it is just as though you didn't have a bitmap
>> (or as though all the bits in the bitmap were set to one).
>
> 	OK, what about the thread in this list where (as I recall) the
> fellow's bitmap was corrupted or lost and it evidently caused the entire
> array to go splat?  That's worrisome.
>
>> The drive filling up is not relevant.  When the bitmap is in a
>> separate file, the file is preallocated to be the right size.
>
> 	Let me take a little different tack.  I don't have any ext2 or ext3
> file systems on the server.  If I am going to set up an external bitmap, I
> am going to have to steal some space from one of the other file systems -
> perhaps from the swap area (5G), the boot file system (reiserfs - 109G), or
> the Windows XP filesystem (NTFS - 40G).  I need to be able to calculate how
> much space to steal to fit the bitmap, and allow for later expansion.

That is pretty flexible and the size is miniscule. For example my big
raid5 with internal bitmap has

      bitmap: 0/233 pages [0KB], 2048KB chunk

That is slightly less than 1MB. With 512MB bitmap I could do 4KB
chunks but from a few tests a larger chunk size is better for me.

MfG
        Goswin

  reply	other threads:[~2009-06-29 10:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  2:10 Write intent bitmaps Leslie Rhorer
2009-06-08 13:51 ` Carlos Carvalho
2009-06-18  8:17   ` Goswin von Brederlow
2009-06-19  2:24     ` Neil Brown
2009-06-19  5:21       ` Goswin von Brederlow
2009-06-19  2:16   ` Neil Brown
2009-06-19 15:01     ` Goswin von Brederlow
2009-06-20  8:14       ` NeilBrown
2009-06-20  9:52         ` Goswin von Brederlow
2009-06-21 18:06     ` Bill Davidsen
2009-06-28 18:14     ` Leslie Rhorer
2009-06-29 10:01       ` Goswin von Brederlow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-23  8:16 RAID 5 recovery to not degrade device on bad block Anshuman Aggarwal
2009-08-24 12:54 ` Goswin von Brederlow
2009-08-24 14:39   ` Write intent bitmaps Simon Jackson
     [not found]     ` <ABFC24E4C13D81489F7F624E14891C860D1F15EF@uk-ex-mbx1.terastack.bluearc .com>
2009-08-24 20:25       ` NeilBrown
2009-09-02 16:10         ` Bill Davidsen
2009-09-02 16:28           ` Paul Clements
2009-09-02 17:36             ` Ryan Wagoner

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=87my7r1hqu.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=carlos@fisica.ufpr.br \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    --cc=neilb@suse.de \
    /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