Regardless of the filesystem (i''ve used reiserfs, xfs, ext3), whenever I mount a fresh DRBD partition I get some nasty kernel messages. This is under Debian Sarge, Xen kernel 2.6.11.12-xen0 (dom0) using DRBD v0.7.11 (pulled from Debian "testing"). This is what I did to create the partition. On both nodes I created a new LVM storage device and started DRBD: # lvcreate -L1G -n drbdtest xen # /etc/init.d/drbd start The rest I did on the primary node. Set the node primary: # drbdadm -- --do-what-I-say primary all Check everything looks fine: # dmesg | tail ; cat /proc/drbd Make the filesystem: # mkfs.ext3 /dev/drbd0 Mount: # mount /dev/drbd0 /mnt/drbd0 Then I get the following kernel messages: Nov 1 13:52:13 localhost kernel: Badness in blk_plug_device at drivers/block/ll_rw_blk.c:1217 Nov 1 13:52:13 localhost kernel: [blk_plug_device+128/144] blk_plug_device+0x80/0x90 Nov 1 13:52:13 localhost kernel: [pg0+140817474/1002423296] drbd_make_request_common+0x6f2/0x8a0 [drbd] Nov 1 13:52:13 localhost kernel: [mempool_alloc+115/432] mempool_alloc+0x73/0x1b0 Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [pg0+140818108/1002423296] drbd_make_request_26+0xcc/0x27d [drbd] Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [generic_make_request+343/496] generic_make_request+0x157/0x1f0 Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [do_anonymous_page+438/544] do_anonymous_page+0x1b6/0x220 Nov 1 13:52:13 localhost kernel: [mempool_alloc+115/432] mempool_alloc+0x73/0x1b0 Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [submit_bio+98/256] submit_bio +0x62/0x100 Nov 1 13:52:13 localhost kernel: [bio_alloc+231/480] bio_alloc +0xe7/0x1e0 Nov 1 13:52:13 localhost kernel: [end_buffer_async_read+0/320] end_buffer_async_read+0x0/0x140 Nov 1 13:52:13 localhost kernel: [submit_bh+213/288] submit_bh +0xd5/0x120 Nov 1 13:52:13 localhost kernel: [block_read_full_page+404/672] block_read_full_page+0x194/0x2a0 Nov 1 13:52:13 localhost kernel: [add_to_page_cache+112/208] add_to_page_cache+0x70/0xd0 Nov 1 13:52:13 localhost kernel: [read_pages+241/320] read_pages +0xf1/0x140 Nov 1 13:52:13 localhost kernel: [blkdev_get_block+0/96] blkdev_get_block+0x0/0x60 Nov 1 13:52:13 localhost kernel: [__alloc_pages+739/1056] __alloc_pages+0x2e3/0x420 Nov 1 13:52:13 localhost kernel: [__do_page_cache_readahead +247/400] __do_page_cache_readahead+0xf7/0x190 Nov 1 13:52:13 localhost kernel: [blockable_page_cache_readahead +58/128] blockable_page_cache_readahead+0x3a /0x80 Nov 1 13:52:13 localhost kernel: [page_cache_readahead+218/720] page_cache_readahead+0xda/0x2d0 Nov 1 13:52:13 localhost kernel: [do_generic_mapping_read +1442/1472] do_generic_mapping_read+0x5a2/0x5c0 Nov 1 13:52:13 localhost kernel: [__generic_file_aio_read+514/576] __generic_file_aio_read+0x202/0x240 Nov 1 13:52:13 localhost kernel: [file_read_actor+0/224] file_read_actor+0x0/0xe0 Nov 1 13:52:13 localhost kernel: [write_buffer+4/64] write_buffer +0x4/0x40 Nov 1 13:52:13 localhost kernel: [generic_file_read+180/208] generic_file_read+0xb4/0xd0 Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [generic_file_read+0/208] generic_file_read+0x0/0xd0 Nov 1 13:52:13 localhost kernel: [vfs_read+174/304] vfs_read+0xae/ 0x130 Nov 1 13:52:13 localhost kernel: [sys_read+81/128] sys_read+0x51/0x80 Nov 1 13:52:13 localhost kernel: [syscall_call+7/11] syscall_call +0x7/0xb Nov 1 13:52:13 localhost kernel: Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1238 Nov 1 13:52:13 localhost kernel: [blk_remove_plug+110/112] blk_remove_plug+0x6e/0x70 Nov 1 13:52:13 localhost kernel: [pg0+140840834/1002423296] drbd_unplug_fn+0x22/0x220 [drbd] Nov 1 13:52:13 localhost kernel: [blk_backing_dev_unplug+25/32] blk_backing_dev_unplug+0x19/0x20 Nov 1 13:52:13 localhost kernel: [block_sync_page+60/80] block_sync_page+0x3c/0x50 Nov 1 13:52:13 localhost kernel: [sync_page+70/80] sync_page+0x46/0x50 Nov 1 13:52:13 localhost kernel: [__wait_on_bit_lock+94/112] __wait_on_bit_lock+0x5e/0x70 Nov 1 13:52:13 localhost kernel: [sync_page+0/80] sync_page+0x0/0x50 Nov 1 13:52:13 localhost kernel: [wake_bit_function+0/96] wake_bit_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [__lock_page+145/160] __lock_page +0x91/0xa0 Nov 1 13:52:13 localhost kernel: [wake_bit_function+0/96] wake_bit_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [page_cache_readahead+218/720] page_cache_readahead+0xda/0x2d0 Nov 1 13:52:13 localhost kernel: [wake_bit_function+0/96] wake_bit_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [find_get_page+53/128] find_get_page+0x35/0x80 Nov 1 13:52:13 localhost kernel: [do_generic_mapping_read +1207/1472] do_generic_mapping_read+0x4b7/0x5c0 Nov 1 13:52:13 localhost kernel: [__generic_file_aio_read+514/576] __generic_file_aio_read+0x202/0x240 Nov 1 13:52:13 localhost kernel: [file_read_actor+0/224] file_read_actor+0x0/0xe0 Nov 1 13:52:13 localhost kernel: [write_buffer+4/64] write_buffer +0x4/0x40 Nov 1 13:52:13 localhost kernel: [generic_file_read+180/208] generic_file_read+0xb4/0xd0 Nov 1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [generic_file_read+0/208] generic_file_read+0x0/0xd0 Nov 1 13:52:13 localhost kernel: [vfs_read+174/304] vfs_read+0xae/ 0x130 Nov 1 13:52:13 localhost kernel: [sys_read+81/128] sys_read+0x51/0x80 Nov 1 13:52:13 localhost kernel: [syscall_call+7/11] syscall_call +0x7/0xb Though, the partition appears to have mounted okay: Nov 1 13:52:13 localhost kernel: kjournald starting. Commit interval 5 seconds Nov 1 13:52:13 localhost kernel: EXT3 FS on drbd0, internal journal Nov 1 13:52:13 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. Any ideas? I saw similar post to the drbd list from last January, but no one had any comments. http://lists.linbit.com/pipermail/drbd-user/2005-January/002436.html I''ve sent this message to drbd-user as well. Thank you. .:. jeremy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Nov 1, 2005, at 2:28 PM, jeremy avnet wrote:> Regardless of the filesystem (i''ve used reiserfs, xfs, ext3), > whenever I mount a fresh DRBD partition I get some nasty kernel > messages. > > This is under Debian Sarge, Xen kernel 2.6.11.12-xen0 (dom0) using > DRBD v0.7.11 (pulled from Debian "testing").Answering my own post in case anyone else runs into this. There is a good chance this problem is indeed related to the bio_clone bug present in 2.6.11.4. Applying the one line patch fixed the problem. However, upgrading to DRBD 0.7.14 also fixed the problem (though it is unclear as to why). For more information about the bio_clone bug and patch see this post: http://www.redhat.com/archives/dm-devel/2005-July/msg00086.html In relation to DRBD see this post: http://lists.linbit.com/pipermail/drbd-user/2005-November/ 004007.html .:. jeremy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Nov 2, 2005, at 1:49 PM, jeremy avnet wrote:> There is a good chance this problem is indeed related to the > bio_clone bug present in 2.6.11.4. Applying the one line patch > fixed the problem. However, upgrading to DRBD 0.7.14 also fixed the > problem (though it is unclear as to why). >uggh, i meant kernel 2.6.11.12 (which is what Xen 2.0.7 uses). .:. jeremy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users