Re: out of vmalloc space - use vmalloc<size> to increase size when mounting xfs FS

[Nathan Scott <nathans@xxxxxxx>]

On Mon, Dec 05, 2005 at 10:27:05AM +0800, Ying-Hung Chen wrote:
> Hi Nathan,
> 
> mount -t xfs /dev/hdb1 /Repository/01
> mount -t xfs /dev/hdc1 /Repository/02
> ...
> 
> [root@localhost ~]# xfs_info /dev/hdb1
> meta-data=/usr/local/MatriVideo/bin/Repository/01 isize=256
> agcount=16, agsize=3052475 blks
>          =                       sectsz=512
> data     =                       bsize=4096   blocks=48839600, imaxpct=25
>          =                       sunit=0      swidth=0 blks, unwritten=1
> naming   =version 2              bsize=4096
> log      =internal               bsize=4096   blocks=23847, version=2
>          =                       sectsz=512   sunit=0 blks

Hmm, I don't understand that then - with these parameters,
your incore log buffers are 32K, which will not cause any
vmalloc calls, which was my first thought at a possible
cause.

I guess you could instrument the __vmalloc code in the
kernel to printk the size parameter and do a dump_stack
when its invoked, and see where all your vmalloc space
is going...

cheers.

-- 
Nathan