[Drbd-dev] Transaction log related assert messages running DRBD 8 trunk

Graham, Simon Simon.Graham at stratus.com
Tue Jul 25 20:56:07 CEST 2006

Running some failover stress testing with the latest DRBD 8, I have
started to notice assert failures like this:

Jul 24 17:36:22 peer kernel: drbd1: ASSERT( b->br_number == barrier_nr )
in drbd/drbd_main.c:280 
Jul 24 17:36:22 peer kernel: drbd1: ASSERT( b->n_req == set_size ) in

I'm not quite sure what these mean, but I do note that the code releases
the spin lock before the assert and it occurs to me that perhaps the
D_ASSERTs should also be done with the lock held (see below)?


--- code from drbd_main.c ---

void tl_release(drbd_dev *mdev,unsigned int barrier_nr,
		       unsigned int set_size)
	struct drbd_barrier *b;


	b = mdev->oldest_barrier;
	mdev->oldest_barrier = b->next;

	/* There could be requests on the list waiting for completion
	   of the write to the local disk, to avoid corruptions of
	   slab's data structures we have to remove the lists head */


	D_ASSERT(b->br_number == barrier_nr);
	D_ASSERT(b->n_req == set_size);

More information about the drbd-dev mailing list