mdadm --grow --bitmap internal attempts to access beyond end of device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When I try to add internal bitmap to an array, mdadm tries to access beyond end of devices and eventually fails to add it.
This bug was fixed in debian unstable, see:
http://
$ uname -provism
Linux 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
$ mdadm --version
mdadm - v3.2.3 - 23rd December 2011
$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid10]
md1 : active raid1 sdb2[2] sdd2[7] sda2[6] sdc2[8] sde2[5]
203764 blocks super 1.0 [5/5] [UUUUU]
<skip>
$ sudo mdadm --grow -b internal /dev/md1
mdadm: failed to set internal bitmap.
$ dmesg | tail
[ 6107.817609] attempt to access beyond end of device
[ 6107.817615] sdb2: rw=16, want=4295374825, limit=407552
[ 6107.817619] attempt to access beyond end of device
[ 6107.817622] sdd2: rw=16, want=4295374825, limit=407552
[ 6107.817625] attempt to access beyond end of device
[ 6107.817628] sda2: rw=16, want=4295374825, limit=407552
[ 6107.817631] attempt to access beyond end of device
[ 6107.817634] sdc2: rw=16, want=4295374825, limit=407552
[ 6107.817637] attempt to access beyond end of device
[ 6107.817640] sde2: rw=16, want=4295374825, limit=407552
-------
debian's 3.2.4-1:
$ mdadm --version
mdadm - v3.2.4 - 9th May 2012
$ sudo mdadm --grow -b internal /dev/md1
$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid10]
md1 : active raid1 sdb2[2] sdd2[7] sda2[6] sdc2[8] sde2[5]
203764 blocks super 1.0 [5/5] [UUUUU]
bitmap: 0/1 pages [0KB], 65536KB chunk
<skip>
Changed in mdadm: | |
status: | New → Confirmed |
On the second thought, debian bug is probably unrelated.