From: Paul Clements <paul.clements@steeleye.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm: bitmaps not supported by this kernel?
Date: Wed, 25 Oct 2006 20:25:15 -0400 [thread overview]
Message-ID: <4540006B.70808@steeleye.com> (raw)
In-Reply-To: <453FD41B.5080908@tls.msk.ru>
Michael Tokarev wrote:
> Another 32/64 bits issue, it seems.
> Running 2.6.18.1 x86-64 kernel and mdadm 2.5.3 (32 bit).
>
> # mdadm -G /dev/md1 --bitmap=internal
> mdadm: bitmaps not supported by this kernel.
>
> # mdadm -G /dev/md1 --bitmap=none
> mdadm: bitmaps not supported by this kernel.
>
> etc.
>
> Recompiling mdadm in 64bit mode eliminates the problem.
I think this is due to the bug I reported a month or so ago. We were
missing a COMPATIBLE_IOCTL entry for the GET_BITMAP_FILE ioctl. Neil has
sent in the patch.
> So far, only bitmap manipulation is broken this way.
> I dunno if other things are broken too - at least
> --assemble, --create, --stop, --detail works.
Yeah, I think everything else works.
--
Paul
prev parent reply other threads:[~2006-10-26 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 21:16 mdadm: bitmaps not supported by this kernel? Michael Tokarev
2006-10-26 0:25 ` Paul Clements [this message]
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=4540006B.70808@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).