From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Linux-Raid <linux-raid@vger.kernel.org>
Subject: Re: why a bitmap file never changes?
Date: Wed, 29 Aug 2007 11:06:34 +0200 [thread overview]
Message-ID: <46D5371A.6020001@wpkg.org> (raw)
In-Reply-To: <46D53228.4000400@wpkg.org>
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%)
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2007-08-29 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 8:45 why a bitmap file never changes? Tomasz Chmielewski
2007-08-29 9:06 ` Tomasz Chmielewski [this message]
2007-08-31 10:32 ` 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=46D5371A.6020001@wpkg.org \
--to=mangoo@wpkg.org \
--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).