* bitmap status question
@ 2006-06-21 17:16 David Greaves
2006-06-21 19:39 ` Paul Clements
0 siblings, 1 reply; 2+ messages in thread
From: David Greaves @ 2006-06-21 17:16 UTC (permalink / raw)
To: linux-raid
How do I interpret:
bitmap: 0/117 pages [0KB], 1024KB chunk
in the mdstat output
what does it mean when it's, eg: 23/117
cu:/huge# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [raid4] [raid6]
md0 : active raid5 sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
hdb1[6](S)
1225543680 blocks level 5, 4096k chunk, algorithm 2 [6/6] [UUUUUU]
bitmap: 0/117 pages [0KB], 1024KB chunk
David
--
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: bitmap status question
2006-06-21 17:16 bitmap status question David Greaves
@ 2006-06-21 19:39 ` Paul Clements
0 siblings, 0 replies; 2+ messages in thread
From: Paul Clements @ 2006-06-21 19:39 UTC (permalink / raw)
To: David Greaves; +Cc: linux-raid
David Greaves wrote:
> How do I interpret:
> bitmap: 0/117 pages [0KB], 1024KB chunk
> in the mdstat output
>
> what does it mean when it's, eg: 23/117
This refers to the in-memory bitmap (basically a cache of what's in the
on-disk bitmap -- it allows bitmap operations to be more efficient).
If it's 23/117 that means there are 23 of 117 pages allocated in the
in-memory bitmap. The pages are allocated on demand, and get freed when
they're empty (all zeroes). The in-memory bitmap uses 16 bits for each
bitmap chunk to count all ongoing writes to the chunk, so it's actually
up to 16 times larger than the on-disk bitmap.
--
Paul
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-06-21 19:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-21 17:16 bitmap status question David Greaves
2006-06-21 19:39 ` Paul Clements
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).