public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Bachmann <grafgrimm77@gmx.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: vmalloc, xfs_buf_get: failed to map pages
Date: Thu, 1 Jul 2010 13:45:30 +0200	[thread overview]
Message-ID: <20100701134530.5f794758@x2.grafnetz> (raw)
In-Reply-To: <20100621072118.GA1361@infradead.org>

Hi again, 

what is a good value for vmalloc= ? 
The machine has 1 GB of RAM. 

Greetings
Mario

Am Mon, 21 Jun 2010 03:21:18 -0400
schrieb Christoph Hellwig <hch@infradead.org>:

> On Sat, Jun 19, 2010 at 03:01:19PM +0200, Mario Bachmann wrote:
> > Hello, 
> > 
> > on a 32bit machine, I have big problems with Linux 2.6.34. 
> > With Linux 2.6.33.4 everything runs fine. 
> > 
> > I do not know where to search for known bugs in xfs.
> > 
> > /var/log/messages shows a lot of lines:
> > 
> > Jun 19 11:43:15 amd2000 kernel: vmap allocation for size 4194304 failed: use vmalloc=<size> to increase size.
> > Jun 19 11:43:15 amd2000 kernel: xfs_buf_get: failed to map pages
> > 
> > What to to?
> 
> Strange.  There have been no fixes to the vmap allocator nor to the
> XFS using this.  What other modules are you ising?  Maybe they increased
> their amount of used vmalloc space.  For now the only thing you can do
> is using the vmalloc= kernel paramter to increase the vmalloc space.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-07-01 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 13:01 vmalloc, xfs_buf_get: failed to map pages Mario Bachmann
2010-06-21  7:21 ` Christoph Hellwig
2010-06-21 11:35   ` Mario Bachmann
2010-07-01 11:45   ` Mario Bachmann [this message]
2010-07-01 13:03     ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100701134530.5f794758@x2.grafnetz \
    --to=grafgrimm77@gmx.de \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox