All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-raid@vger.kernel.org, neilb@suse.de
Subject: Re: Some RAID levels do not support bitmap
Date: Mon, 11 Jun 2007 19:15:59 -0400	[thread overview]
Message-ID: <466DD7AF.7030107@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706111448500.19578@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> Hi,
>
>
> RAID levels 0 and 4 do not seem to like the -b internal. Is this 
> intentional? Runs 2.6.20.2 on i586.
> (BTW, do you already have a PAGE_SIZE=8K fix?)
>
> 14:47 ichi:/dev # mdadm -C /dev/md0 -l 4 -e 1.0 -b internal -n 2 /dev/ram[01]
> mdadm: RUN_ARRAY failed: Input/output error
> mdadm: stopped /dev/md0
> 14:47 ichi:/dev # mdadm -C /dev/md0 -l 0 -e 1.0 -b internal -n 2 /dev/ram[01]
> mdadm: RUN_ARRAY failed: Cannot allocate memory
> mdadm: stopped /dev/md0
>
> Right... md: bitmaps not supported for this level.
>   

Bitmaps show what data has been modified but not written. For RAID-0 
there is no copy, therefore there can be no bitmap to show what "still 
needs to be updated." I would have thought that RAID-4 would support 
bitmaps, but maybe it was just never added because use of RAID-4 is 
pretty uncommon.

BTW: RAID-4 seems to work fine with an external bitmap. Were you trying 
to do "internal?"

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2007-06-11 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 12:50 Some RAID levels do not support bitmap Jan Engelhardt
2007-06-11 23:15 ` Bill Davidsen [this message]
2007-06-11 23:39   ` Neil Brown
2007-06-12 15:52     ` Bill Davidsen

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=466DD7AF.7030107@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-raid@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.