On Thu, 17 Dec 1998, David Harris wrote:
> It seems that you are saying that there are two states of the resync speed:
> (1) full resync speed which only happens after a full second of IO silence,
> and (2) the guaranteed minimum bandwidth resync speed. Are there any shades
> of gray in between?
l devices are overlapping on my system, so this
seems weird. Could you just explain this unit and how it applies.
Thanks,
- David Harris
Principal Engineer, DRH Internet Services
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of MOLNAR Ingo
Sent: Th
On Wed, 16 Dec 1998 [EMAIL PROTECTED] wrote:
> > The resync uses all available unused I/O bandwidth. You cannot speed that
> > up, besides adding faster hardware :)
>
> It doesn't seem to... when the mke2fs is going and pounding the drives
> all 9 access lights are pegged, but the backgroun
> The resync uses all available unused I/O bandwidth. You cannot speed that
> up, besides adding faster hardware :)
It doesn't seem to... when the mke2fs is going and pounding the drives
all 9 access lights are pegged, but the background resync only writes
to the drives around once a second,
after mkraid --really-force'ing a new md0 (diff chunk size - 256k)
and doing a mke2fs -b 4096 -R stride=64, I noticed that the
finish= time in /proc/mdstat still runs into the hundreds of minutes.
Would bonnie results on a md0 that's at "resync=9% finish=552.9min"
be valid? Can I force it to hur
