Re: Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components? | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Ty! Boyack wrote:
<snip> Right now, without the automation, it is possible, and likely, that an operator cannot respond in time to avoid having the bitmap fill up, and then we are into a long resync.
The bitmap can not "fill-up" - this is by design. It is created by simply subdividing the _entire_ array into a number of equally sized regions (the exact amount depends on the bitmap size, and the size of every region depends on the md device size). Then any time a write operation touches the disk the corresponding region is marked as dirty. There might be one write or a thousand writes - as long as they all fall within the same region - it is the only one which will be resync-ed.
HTH Peter -- 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
[Home] [ATA RAID] [Linux] [Managing RAID on Linux] [Linux IDE] [Linux SCSI] [Linux Hams] [Device-Mapper] [Kernel] [Linux Books] [Linux Admin] [Linux Net] [GFS] [RPM] [Photos] [Yosemite Photos] [Yosemite News] [AMD 64] [Linux Nework]
![]() |