[DRBD-user] Re: STOP_SYNC_TIMER was set in _drbd_rs_resume, but rs_left still 303

Bernd Schubert bs at q-leap.de
Mon Oct 8 10:53:10 CEST 2007

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

Lars Ellenberg wrote:

> On Thu, Oct 04, 2007 at 09:04:54PM +0200, Bernd Schubert wrote:
>> Hi,
>> is this something to worry about?
>> [18797.912631] drbd1: _drbd_rs_resume: (stop_syncer_timer_was_set) in
>> [drivers/block/drbd/drbd_worker.c:700 18797.922480] drbd1:
>> [STOP_SYNC_TIMER was set in _drbd_rs_resume, but rs_left still 303
>> [18798.935707] drbd1: Resync done (total 12 sec; paused 0 sec; 716 K/sec)
>> [18798.968892] drbd1: drbd1_worker [17380]: cstate SyncTarget -->
>> [Connected 18798.976145] drbd1: Avoided requeue of resync_work
>> Did happen on a secondary device after a networking failure with
>> drbd-0.7.23.
> I think its a harmless warning message we left in place do gather more
> info about some harmless but annoying race during, well, connection
> failure during sync.

Ah, this explains it. Its drbd over IPoIB and there had been infininband
problems and I had to restart opensm several times.

> we should probably have been more specific under which circumstances we
> want to log this scary message...

Thank a lot for your help,

More information about the drbd-user mailing list