On Fri, 24 Aug 2007, Tomasz Chmielewski wrote:
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
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Check: http://lkml.org/lkml/2007/6/17/235
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
