Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jan 05, 2010 at 04:59:31PM +0000, Sven Geggus wrote:
> Lars Ellenberg <lars.ellenberg at linbit.com> wrote:
>
> > run autoheader once
>
> OK, at least this works.
> Do I still need to use vmalloc=256M Kernel parameter?
nope. no need for that with DRBD 8.3
> >> Any hint on how to fix this?
> >
> > how about enable large block devices in your kernel?
> > hey, just asking... you know, sometimes it is just too easy to see :)
>
> Unfortunately its not that easy:
>
> ~/ # grep LBD /boot/config-2.6.32.2
> CONFIG_LBDAF=y
outch.
now, _this_ is embarrassing :/
thanks for persevering!
I thought we had a regression test on that. oh well...
commit 9fbaeab2647cdab8cfe38188f34e45196dec9768
Author: Lars Ellenberg <lars.ellenberg at linbit.com>
Date: Tue Jan 5 19:33:54 2010 +0100
drbd: check on CONFIG_LBDAF, not LBD
It is called LBDAF since 2.6.31.
impact:
without this change, on 32bit,
DRBD would wrongly claim to only support 4TiB devices.
diff --git a/drbd/drbd_int.h b/drbd/drbd_int.h
index 8fcce0f..d0bf35c 100644
--- a/drbd/drbd_int.h
+++ b/drbd/drbd_int.h
@@ -1437,7 +1437,7 @@ struct bm_extent {
#if DRBD_MAX_SECTORS_BM < DRBD_MAX_SECTORS_32
#define DRBD_MAX_SECTORS DRBD_MAX_SECTORS_BM
#define DRBD_MAX_SECTORS_FLEX DRBD_MAX_SECTORS_BM
-#elif !defined(CONFIG_LBD) && BITS_PER_LONG == 32
+#elif !defined(CONFIG_LBDAF) && !defined(CONFIG_LBD) && BITS_PER_LONG == 32
#define DRBD_MAX_SECTORS DRBD_MAX_SECTORS_32
#define DRBD_MAX_SECTORS_FLEX DRBD_MAX_SECTORS_32
#else
--
: 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