All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Incorrect in-kernel bitmap on raid10
Date: Sat, 18 Apr 2009 20:15:25 +0200	[thread overview]
Message-ID: <slrnguk663.8bq.Mario.Holbe@darkside.dyn.samba-tng.org> (raw)

Hello,

I created a 4.5T RAID10 with internal bitmap out of 3 1.5T disks on a
Debian 2.6.28-1-686-bigmem kernel:
# mdadm --create -l raid10 -n 6 -c 512 -b internal -a md /dev/md7 /dev/sdc1 missing /dev/sdd1 missing /dev/sde1 missing
and I get a strange inconsistency between the on-disk and the in-kernel
bitmap representation:
[202617.869531] md: bind<sdc1>
[202617.888998] md: bind<sdd1>
[202617.908895] md: bind<sde1>
[202617.917307] md: md7: raid array is not clean -- starting background reconstruction
[202619.527127] md: raid10 personality registered for level 10
[202619.544588] raid10: raid set md7 active with 3 out of 6 devices
[202619.563536] md7: bitmap file is out of date (0 < 1) -- forcing full recovery
[202619.584919] md7: bitmap file is out of date, doing full recovery
[202619.655867] md7: bitmap initialized from disk: read 1/1 pages, set 6131 bits
[202619.677268] created bitmap (3 pages) for device md7
[202619.714033] md7: detected capacity change from 0 to 4500896612352
[202619.732554]  md7: unknown partition table
[202781.236591] md: resync of RAID array md7
[202781.248610] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[202781.266343] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
[202781.294735] md: using 128k window, over a total of 4395406848 blocks.
[202781.336808] md: md7: resync done.
[202781.347708] md7: invalid bitmap page request: 3 (> 2)
[202781.363228] md7: invalid bitmap page request: 3 (> 2)
[202781.378637] md7: invalid bitmap page request: 3 (> 2)
[202781.394286] md7: invalid bitmap page request: 3 (> 2)
[202781.409704] md7: invalid bitmap page request: 3 (> 2)
...lots more of them...
[202781.832046] md7: invalid bitmap page request: 129 (> 2)
[202781.832047] md7: invalid bitmap page request: 129 (> 2)
[202781.832048] md7: invalid bitmap page request: 129 (> 2)
[202781.832049] md7: invalid bitmap page request: 129 (> 2)
[202781.832050] md7: invalid bitmap page request: 129 (> 2)
...lots more of them...
[202781.832095] md7: invalid bitmap page request: 130 (> 2)
[202781.832096] md7: invalid bitmap page request: 130 (> 2)
[202781.832097] md7: invalid bitmap page request: 130 (> 2)
[202781.832097] md7: invalid bitmap page request: 130 (> 2)
[202781.832098] md7: invalid bitmap page request: 130 (> 2)
...lots more of them...

While mdadm -X on every component shows a reasonable bitmap with a 16M
chunk size and 268275 chunks, the kernel seems to assume there are only
6131 chunks and initializes 3 instead of 130 pages.

The same happens when adding the bitmap with -G -b internal to an
existing array.

I don't know if this problem belongs to the array size (i.e. some 32bit
boundary problem) or to raid10 in general.


regards
   Mario
-- 
<snupidity> bjmg: ja, logik ist mein fachgebiet. das liegt im gen
<uepsie> in welchem?
<snupidity> im zweiten X


             reply	other threads:[~2009-04-18 18:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18 18:15 Mario 'BitKoenig' Holbe [this message]
2009-04-19  6:24 ` Incorrect in-kernel bitmap on raid10 Neil Brown
2009-04-19 22:55   ` Mario 'BitKoenig' Holbe
2009-04-19 23:27     ` Neil Brown
2009-04-20  0:13       ` Race condition in write_sb_page? (was: Re: Incorrect in-kernel bitmap on raid10) Mario 'BitKoenig' Holbe
2009-04-20  1:57         ` NeilBrown
2009-04-20  8:03           ` Race condition in write_sb_page? Mario 'BitKoenig' Holbe
2009-04-22 18:45   ` Incorrect in-kernel bitmap on raid10 Mario 'BitKoenig' Holbe
2009-04-28 14:05     ` Mario 'BitKoenig' Holbe
2009-05-01  2:11       ` Neil Brown
2009-05-01 17:55         ` Mario 'BitKoenig' Holbe
2009-05-01 21:36           ` NeilBrown
2009-05-02 19:52             ` Mario 'BitKoenig' Holbe
2009-05-02 22:41               ` NeilBrown
2009-05-03 13:22                 ` Mario 'BitKoenig' Holbe
2009-05-07 20:25                   ` Mario 'BitKoenig' Holbe

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=slrnguk663.8bq.Mario.Holbe@darkside.dyn.samba-tng.org \
    --to=mario.holbe@tu-ilmenau.de \
    --cc=linux-raid@vger.kernel.org \
    /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.