[DRBD-user] resyncing, bandwidth limits and new writes.

atp Andrew.Phillips at lmax.com
Mon Apr 26 11:05:11 CEST 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


  I have a pair of systems which provide a resilient NFS service. 

When I bring in a new secondary system, I need to resync the volumes 
across from the primary, yet still maintain service to the NFS clients.

The question is; is using the bandwidth limit helpful or counter
productive? Ideally I'd like to bias for current writes from clients via
the primary, with the resync happening in the background.

We have tried setting the resync bandwidth lower, but this does not seem
to help. Are "current writes" part of the same bandwidth? Is there a way
to prioritise them over background resync traffic?

  Hope thats clear.


Andrew Phillips
Head of Systems


Office: +44 203 1922509
Mobile: +44 (0)7595 242 900

LMAX | Level 2, Yellow Building | 1 Nicholas Road | London | W11 4AN

The information in this e-mail and any attachment is confidential and is intended only for the named recipient(s). The e-mail may not be disclosed or used by any person other than the addressee, nor may it be copied in any way. If you are not a named recipient please notify the sender immediately and delete any copies of this message. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any view or opinions presented are solely those of the author and do not necessarily represent those of the company.

More information about the drbd-user mailing list