Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Dec 07, 2009 at 07:26:46PM -0800, Vadym Chepkov wrote: > I never specified any block size or modified any non-default > parameters during compilation. Should I compile drbd differently and > include some flags to reduce per bio size? You did nothing wrong. It is DRBD that does some stupid things under certain circumstances, apparently. > This is from dmesg output > > drbd: initialized. Version: 8.3.5 (api:88/proto:86-91) > drbd: GIT-hash: ded8cdf09b0efa1460e8ce7a72327c60ff2210fb build by vchepkov at ashlin02, 2009-12-05 19:33:37 > drbd: registered as block device major 147 > drbd: minor_table @ 0xc0000000ea5e7380 > blk_queue_max_segment_size: set to minimum 65536 > block drbd0: Starting worker thread (from cqueue/0 [292]) > block drbd0: disk( Diskless -> Attaching ) > block drbd0: No usable activity log found. > block drbd0: Method to ensure write ordering: barrier > blk_queue_max_sectors: set to minimum 128 > blk_queue_max_segment_size: set to minimum 65536 > block drbd0: max_segment_size ( = BIO size ) = 65536 uh. I'd like to know your exact kernel version. If not a "standard" kernel, I'd need your kernel config. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed