Tomasz Chmielewski schrieb:
Tomasz Chmielewski schrieb:
The date of the file is the date of creation of this array, and as I
look inside, it's basically almost empty. When looking in a hex
editor, zeroes (+bitm etc.)at the beginning, and than FF to the end.
Is it normal?
Here is some more info about the bitmap itself - it's 100% dirty, what
does it mean?
# mdadm -X /root/backup-bitmap
Filename : /root/backup-bitmap
Magic : 6d746962
Version : 4
UUID : 00000000.00000000.00000000.00000000
Events : 0
Events Cleared : 0
State : OK
Chunksize : 1 MB
Daemon : 5s flush period
Write Mode : Allow write behind, max 256
Sync Size : 658800640 (628.28 GiB 674.61 GB)
Bitmap : 643360 bits (chunks), 643360 dirty (100.0%)
After the drives synchronized, the bitmap file was no longer 100% dirty.
So, I guess it gets 100% dirty when there is a substantial activity
going on? Like resync, for example.
--
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
