Re: mdadm failed to remove internal bitmap

[NeilBrown <neilb@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Mon, 16 Feb 2015 14:42:20 +0800 gary <gary.mdjiang@gmail.com> wrote:

> Hi Neil,
> 
> Please check the followings.
> > What kernel are you running?
> linux48:~ # uname -r
> 3.12.32-33-default

Does this have any patches on top of 3.12.32 that touch md.c ?


> 
> And 3.12.28-4-default kernel is ok.

There are no differences between 3.12.28 and 3.12.32 that could affect this.


> ioctl(3, RAID_VERSION, 0x7fff2e10c060)  = 0
> ioctl(3, GET_BITMAP_FILE, 0x7fff2e10c1f0) = 0
> ioctl(3, GET_ARRAY_INFO, 0x7fff2e10c1a0) = 0
> ioctl(3, SET_ARRAY_INFO, 0x7fff2e10c1a0) = -1 EINVAL (Invalid argument)
> write(2, "mdadm: failed to remove internal"..., 41mdadm: failed to 
> remove internal bitmap.


EINVAL from SET_ARRAY_INFO almost certainly comes from update_array_info().
It can happen if:
 - more than 1 thing needs to be updated - seems unlikely
 - pers->quiesce is NULL - not possible for raid1.
 - mddev->bitmap->storage.file is not NULL.  Seems unlikely.

I suggest you look at the code you are actually running, and possible add
some printks to tell you where it is failing.

NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]