All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volker <mail@blafoo.org>
Cc: xfs@oss.sgi.com
Subject: Re: OOM on quotacheck (again?)
Date: Thu, 20 Sep 2012 11:32:17 +0200	[thread overview]
Message-ID: <505AE2A1.5060703@blafoo.org> (raw)
In-Reply-To: <20120919205924.GC31501@dastard>

Hi,

> Which implies you are running a 32 bit kernel even on 64 bit CPUs
> (e.g. R710).

My mistake. That is not yet the case, but the plan for the future.
Thanks for pointing that out.

> No surprise if you are running an i686 kernel (32 bit). You've got
> way more inodes than can fit in the kernel memory segment.

Could you slightly elaborate on that or give me a link or two which
explain the matter?

If a 32bit kernel is not supposed to work because of the number of
inodes, why does the 2.6.39.4-kernel work flawlessy on quota-checks on
the same filesystem a 3.6.0-rc5 32bit (which is supposed to work) fails on?

Doesn't that imply, that the fix submitted for 2.6.39.4 fixed a problem
which was "reinvented" by the later patch, which is now being worked
around by using a 64bit kernel for more memory?

> Running on a x86-64 kernel will make the vmalloc problem go away.
> There's very little we can do about the limited vmalloc address
> space on i686 kernels. As it is, the known recent regression in this
> space:
> 
> bcf62ab xfs: Fix overallocation in xfs_buf_allocate_memory()
> 
> $ git describe --contains bcf62ab
> v3.6-rc1~42^2~35
> 
> was fixed in 3.6-rc1, 

Confirmed. The current 3.6.0-rc5 in 64bit works doing the quota-check.
I'll do some more testing with xfs_fsr etc. and report back.

best regards
volker

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

  reply	other threads:[~2012-09-20  9:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 14:12 OOM on quotacheck (again?) blafoo
2012-09-19 20:59 ` Dave Chinner
2012-09-20  9:32   ` Volker [this message]
2012-09-24 13:21     ` Dave Chinner
2012-09-24 14:47       ` Volker
2012-10-02 16:29         ` Volker
2012-10-02 20:09           ` Dave Chinner
2012-10-02 20:49             ` Volker
2012-10-02 22:15               ` Dave Chinner
2012-10-04 14:19                 ` Volker

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=505AE2A1.5060703@blafoo.org \
    --to=mail@blafoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.