Re: Kernel oops adding bitmap

Btw, was interested in, where bitmap will be placed when adding it on
live array? I.e. as it requires some diskspace, we should provide some
free space, but where it can be taken from if array is already created
and used by, say filesystem?

On Tue, Mar 20, 2012 at 1:40 AM, Larkin Lowrey
[off-list ref] wrote:

On 3/19/2012 4:32 PM, NeilBrown wrote:

quoted

On Mon, 19 Mar 2012 11:44:45 -0500 Larkin Lowrey

[off-list ref]

quoted

wrote:

quoted

The following command oopsed.

mdadm -G --bitmap=internal /dev/md0

The array is a two disk raid1 and hosts the root filesystem.

Is it not possible/allowed to add a bitmap to an active/mounted array?

It is. But it is busted.

Either use an older mdadm (3.2.2 or earlier), or apply this patch

http://neil.brown.name/git?p=md;a=commitdiff;h=4474ca42e2577563a919fd3ed782e2ec55bf11a2

which has been sent to Linus already and should appear in -stable

kernels in

quoted

a couple of weeks.

NeilBrown

Thank you for the explanation.

--Larkin

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html