linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent CARON <lcaron@apartia.fr>
To: linux-raid@vger.kernel.org
Cc: Luca Berra <bluca@comedia.it>
Subject: Re: Bitmaps & Kernel Versions
Date: Thu, 16 Mar 2006 12:56:37 +0100	[thread overview]
Message-ID: <44195275.9010208@apartia.fr> (raw)
In-Reply-To: <20060315234333.GC25405@percy.comedia.it>

Luca Berra a écrit :
> On Wed, Mar 15, 2006 at 09:08:17PM +1100, Neil Brown wrote:
> 
>> On Wednesday March 15, lcaron@unix-scripts.info wrote:
>>
>>> Hi,
>>>
>>> I'm planning to use bitmaps on some of our RAID1 arrays.
>>>
>>> I'm wondering how bitmaps are handeled by older kernels.
>>>
>>> Eg: I create a raid array with a bitmap under a 2.6.15 kernel.
>>>
>>> I now want to boot under 2.6.12, or even 2.4
>>>
>>>
>>> Hos is it handeled?
>>> Will it work even if this is my / partition?
>>
>>
>> On older kernel will not notice the bitmap and will behave
>> 'normally'.
> 
> strange,
> last time i tried an older kernel would refuse to activate an md with a
> bitmap on it.
> I am far from home on a business trip and i don't have kernel-sources at
> hand, but i seem to remember that the kernel was very strict on the
> feature bitmap in the superblock.
> 
> L.
> 
I experienced the same strange behavior.

Bitmap was created on 2.6.15, tried to boot 2.6.14 and /dev/md0 was not 
started :$.

Strange.....
-
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

      reply	other threads:[~2006-03-16 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15  9:12 Bitmaps & Kernel Versions Laurent CARON
2006-03-15 10:08 ` Neil Brown
2006-03-15 23:43   ` Luca Berra
2006-03-16 11:56     ` Laurent CARON [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=44195275.9010208@apartia.fr \
    --to=lcaron@apartia.fr \
    --cc=bluca@comedia.it \
    --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 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).