Mike Snitzer wrote:
On 7/26/06, Paul Clements <[EMAIL PROTECTED]> wrote:
Mike Snitzer wrote:
> Also, what is the interface one should use to collect dirty bits from
> the primary's bitmap?
Whatever you'd like. scp the bitmap file over or collect the ranges into
a file and scp that over, or something similar.
OK, so regardless of whether you are using an external or internal
bitmap; how does one collect the ranges from an array's bitmap?
Well, with an internal bitmap you don't need this interface. The bitmap
is located on all the component disks. The reason we don't use internal
bitmaps in a configuration where one of the disks is located remotely
(over a LAN or SAN, or possibly a WAN) is that the bitmap updates (which
are synchronous and occur fairly often) would be too costly.
So reading the bits out of a file is fairly simple. The bitmap file is
laid out one bit per chunk, with a 256 byte superblock at the front. You
just need a perl script (for example) that reads the file and keeps
track of which bits are dirty, and then prints those numbers out.
--
Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
