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

Lars Ellenberg lars.ellenberg at linbit.com
Fri Oct 5 14:24:32 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.

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.

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

: Lars Ellenberg                           http://www.linbit.com :
: DRBD/HA support and consulting             sales at linbit.com :
: LINBIT Information Technologies GmbH      Tel +43-1-8178292-0  :
: Vivenotgasse 48, A-1120 Vienna/Europe     Fax +43-1-8178292-82 :
please use the "List-Reply" function of your email client.

More information about the drbd-user mailing list