From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: linux-raid@vger.kernel.org
Subject: simple question: where is internal bitmap stored?
Date: Wed, 13 May 2009 18:37:12 +1000 [thread overview]
Message-ID: <4A0A86B8.5030905@eyal.emu.id.au> (raw)
If I have a live raid and want to enable bitmap then I do
mdadm --grow /dev/md0 --bitmap=internal
Does this bitmap use space in the already present header? If so then
does this mean that the headers have enough reserve for this? Why
not always use the bitmap then?
If it carves extra space from the device which already has data
(e.g. a fs) then surely this will be problematic.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au)
next reply other threads:[~2009-05-13 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 8:37 Eyal Lebedinsky [this message]
2009-05-13 10:42 ` simple question: where is internal bitmap stored? Neil Brown
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=4A0A86B8.5030905@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--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