The following information would be useful for debugging: - Internal or external meta data? - Any special activity log configuration, like a striped AL, different AL stripe size, etc.? - Any manually configured number of AL extents? - Value of max-peers - Reported size of the DRBD device in sectors - Reported size of the backend device for DRBD in sectors - Ideally, a 'drbdadm dump-md' of the meta data of the affected devices
br, Robert On 08/14/2018 10:02 AM, Yannis Milios wrote: > Does this happen on both nodes? What’s the status of the backing > device (lvm) ? Can you post the exact versions for both kernel module > and utils? Any clue in the logs? > > On Tue, 14 Aug 2018 at 06:57, Oleksiy Evin <[email protected] > <mailto:[email protected]>> wrote: > > > # drbdadm attach all > extent 19136522 beyond end of bitmap! > extent 19143798 beyond end of bitmap! > extent 19151565 beyond end of bitmap! > > ../shared/drbdmeta.c:2279:apply_al: ASSERT(bm_pos - bm_on_disk_pos > <= chunk - extents_size) failed. > _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
