Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Am Donnerstag, 20. April 2006 14:33 schrieb Michael Paesold: > Ard van Breemen wrote: > > drbd bef b->bm=ffffc200005ba000,page_nr=2947 > > drbd aft b->bm=ffffc200005ba000,page_nr=2947 > > drbd bef b->bm=ffffc200005ba000,page_nr=2948 > > drbd aft b->bm=ffffc200005ba000,page_nr=2948 > > drbd0: reading of bitmap took 2374 jiffies > > drbd0: recounting of set bits took additional 2 jiffies > > drbd0: 368 GB marked out-of-sync by on disk bit-map. > > drbd0: No usable activity log found. > > drbd0: disk( Attaching -> Inconsistent ) > > drbd0: BUG! md_sync_timer expired! Worker calls drbd_md_sync(). > > drbd0: Writing meta data super block now. > > drbd0: BUG! md_sync_timer expired! Worker calls drbd_md_sync(). > > What is this last log line about? I just tried to resize a drbd devices > (after having extended the underlying LVM device) and got this: > > Apr 20 14:14:31 xen01 kernel: drbd1: Moving meta-data. > Apr 20 14:14:31 xen01 kernel: drbd1: writing of bitmap took 10 jiffies > Apr 20 14:14:31 xen01 kernel: drbd1: 0 KB marked out-of-sync by on disk bit-map. > Apr 20 14:14:31 xen01 kernel: drbd1: 0 KB now marked out-of-sync by on disk bit-map. > Apr 20 14:14:31 xen01 kernel: drbd1: Writing meta data super block now. > Apr 20 14:14:31 xen01 kernel: drbd1: drbd_bm_resize called with capacity == 35650424 > Apr 20 14:14:31 xen01 kernel: drbd1: resync bitmap: bits=4456303 words=139260 > Apr 20 14:14:31 xen01 kernel: drbd1: size = 16 GB (17825212 KB) > Apr 20 14:14:31 xen01 kernel: drbd1: writing of bitmap took 1 jiffies > Apr 20 14:14:31 xen01 kernel: drbd1: 2047 MB marked out-of-sync by on disk bit-map. > Apr 20 14:14:31 xen01 kernel: drbd1: 2097088 KB now marked out-of-sync by on disk bit-map. > Apr 20 14:14:36 xen01 kernel: drbd1: BUG! md_sync_timer expired! Worker calls drbd_md_sync(). > Apr 20 14:14:36 xen01 kernel: drbd1: Writing meta data super block now. > That means that there somewhere in the code thet should be a call do drbd_md_sync(). After a second there md_sync_timer expired and a fallback mechanism called drbd_md_sync(). Before drbd-8.0 becomes stable we should find all those missing calls to drbd_md_sync(). The "damage" of the bug was corrected by the fallback-mechanism, so no need to worry for you. -philipp -- : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :