From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
Linux-Raid <linux-raid@vger.kernel.org>
Subject: Re: recovery starts from 0 after reboot - normal?
Date: Fri, 24 Aug 2007 13:46:35 +0200 [thread overview]
Message-ID: <46CEC51B.10105@wpkg.org> (raw)
In-Reply-To: <46CEC231.1070407@wpkg.org>
Tomasz Chmielewski schrieb:
(...)
> Perhaps, the bitmap is needed then? I guess by default, no internal
> bitmap is added?
>
> # mdadm -X /dev/md0
> Filename : /dev/md0
> Magic : 00000000
> mdadm: invalid bitmap magic 0x0, the bitmap file appears to be corrupted
> Version : 0
> mdadm: unknown bitmap version 0, either the bitmap file is corrupted or
> you need to upgrade your tools
>
>
> The fine manual says:
>
> BITMAP CHANGES
> A write-intent bitmap can be added to, or removed from, an active
> array. Either internal bitmaps, or bitmaps stored in a separate file
> can be added.
>
>
> However, I'm not sure how to achieve it? How to add an internal bitmap
> to an array without a bitmap?
According to the fine manual, BITMAP CHANGES belong to the grow mode.
So, let's try to do what the manual says - try to add a bitmap to the
active array:
# mdadm --grow /dev/md0 --bitmap=internal
mdadm: failed to set internal bitmap.
# dmesg
md: couldn't update array info. -16
So, either I don't understand the manual, or there are more caveats in it.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2007-08-24 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 11:20 recovery starts from 0 after reboot - normal? Tomasz Chmielewski
2007-08-24 11:22 ` Justin Piszcz
2007-08-24 11:34 ` Tomasz Chmielewski
2007-08-24 11:40 ` Justin Piszcz
2007-08-24 11:46 ` Tomasz Chmielewski [this message]
2007-08-24 11:48 ` Justin Piszcz
2007-08-24 11:59 ` Tomasz Chmielewski
2007-08-27 13:39 ` Tomasz Chmielewski
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=46CEC51B.10105@wpkg.org \
--to=mangoo@wpkg.org \
--cc=jpiszcz@lucidpixels.com \
--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).