On 28 May 2012 12:03, Igor M Podlesny <for.poige+lsr@xxxxxxxxx> wrote:
> On 28 May 2012 10:54, NeilBrown <neilb@xxxxxxx> wrote:
> [...]
>> The best indicator is total time that it takes (which can probably be
>> extracted from logs as start and end are logged). Divide that into size of a
>> device to get average MB/sec. If the bitmap was used, that will normally be
>> much less the best throughput of the device.
>
> That's exactly why I am stating it didn't use WIBs 2 times of 3. It
> went resyncing from beginning till the end -- I had my finger on its
> pulse. :)
>
> I can't promise (due to popular "lack of time" disease, yeah), but
> if I'll get on it using VirtualBox or real environment [Lord forbid
> :)] once again, I'll let you know, sure.
Here it is: http://pastie.org/4118133
— 3.4.2-rt10 went suspend ok for 2 times, the 3rd it didn't.
Reboot, resync, no bitmaps use.
And, BTW, it's rather slow in despite of having max. stripe_cache_size set.
--
--
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
[ATA RAID]
[Linux SCSI Target Infrastructure]
[Managing RAID on Linux]
[Linux IDE]
[Linux SCSI]
[Linux Hams]
[Device-Mapper]
[Kernel]
[Linux Books]
[Linux Admin]
[Linux Net]
[GFS]
[RPM]
[git]
[Photos]
[Yosemite Photos]
[Yosemite News]
[AMD 64]
[Linux Networking]