Tomasz Chmielewski schrieb:
Justin Piszcz schrieb:
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.
(...)
Check: http://lkml.org/lkml/2007/6/17/235
It's an external bitmap; I'd prefer an internal one, as my root
filesystem is on a flash-IDE disk.
However, let's try the external bitmap:
# mdadm --grow /dev/md0 --bitmap=/bitmapfile
mdadm: Cannot set bitmap file for /dev/md0: Device or resource busy
So, it also fails. Perhaps because the array still rebuilds?
It looks it only works when the array is in a clean state (or, not
rebuilding anymore).
Just for reference:
# mdadm --grow --bitmap=/bitmapfile /dev/md0
# dmesg -c
md0: bitmap file is out of date (0 < 43130) -- forcing full recovery
md0: bitmap file is out of date, doing full recovery
md0: bitmap initialized from disk: read 24/24 pages, set 763103 bits,
status: 0
created bitmap (373 pages) for device md0
# mdadm --grow /dev/md0 --bitmap=internal
mdadm: /dev/md0 already has a bitmap (/bitmapfile)
# mdadm --grow /dev/md0 --bitmap=none
# mdadm --grow /dev/md0 --bitmap=internal
# dmesg -c
md0: bitmap file is out of date (0 < 43130) -- forcing full recovery
md0: bitmap file is out of date, doing full recovery
md0: bitmap initialized from disk: read 12/12 pages, set 381552 bits,
status: 0
created bitmap (187 pages) for device md0
What are pages/bits in bitmap? It seems to differ, whether internal or
external is used.
--
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
