Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Me said:
> Next step: I used the functionality of the RAID Controller to create <2TB
> volumes. Thus I now have 3 disks (sde/sdf/sdg), each with 1,5TB.
>
> drbd still fails to start r2.
>
> Starting DRBD resources: [ d0 d1 d2 ioctl(,SET_DISK_CONFIG,) failed:
> Cannot allocate memory
>
> cmd /sbin/drbdsetup /dev/drbd2 disk /dev/sdg1 internal -1
> --on-io-error=detach failed!
>
> /var/log/messages is a bit more verbose:
>
> 42949598.710000] allocation failed: out of vmalloc space - use
> vmalloc=<size> to increase size.
> [42949598.710000] drbd2: OUT OF MEMORY! Could not allocate bitmap! Set
> device size => 0
>
> This seems to be an FAQ:
>
> http://www.linux-ha.org/DRBD/FAQ#head-c6586035cbdd5cdae726b02406b838ee2fa56eae
>
> | What is warning: ''out of vmalloc space''
> |
> | For each device, drbd will (try to) allocate X MB of bitmap, plus some
> | constant amount (<1MB). X = storage_size_in_GB/32, so 1 TB storage -> 32
> | MB bitmap.
> |
> | By default Linux allocates 128MB to Vmalloc. For systems using more than
> | 4TB, this may cause an issue.
> |
> | If you get the following error message in /var/log/messages, Try a Linux
> | 2.6 hugemem kernel.
> |
> | kernel: allocation failed: out of vmalloc space - use vmalloc=<size> to
> | increase size.
>
> I tried this two kernel images that are available for ubuntu 6.06.
>
> 2.6.15-26-server
> 2.6.15-27-686
>
> I can't find anything about hugemem support on the ubuntu web pages or the
> ubuntu wiki.
>
> Anyone using ubunto or debian? Do I have to compile a custom kernel to get
> this working?
I'm sorry to reply to my own post once again...
I found something in the list archives about using vmalloc=192m in grub's
menu.lst.
VmallocTotal: 180216 kB
VmallocUsed: 140608 kB
VmallocChunk: 39220 kB
This worked.
rsion: 0.7.15 (api:77/proto:74)
SVN Revision: 2020 build by root at ubuntu7600, 2006-11-10 16:36:11
0: cs:WFConnection st:Secondary/Unknown ld:Inconsistent
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
1: cs:WFConnection st:Secondary/Unknown ld:Inconsistent
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
2: cs:WFConnection st:Secondary/Unknown ld:Inconsistent
ns:0 nr:0 dw:0 dr:0 al:0 bm:178798 lo:0 pe:0 ua:0 ap:0
Is there any downside using this option?
Ralf