public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ADH <swing@adminsend.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Major XFS problems...
Date: Sat, 11 Sep 2004 11:21:37 +0200	[thread overview]
Message-ID: <4142C3A1.1010005@adminsend.de> (raw)
In-Reply-To: <2Cdl9-4Pc-65@gated-at.bofh.it>

Hmm,

looks like probs I had recently on big filesystems under load on a smp 
machine. the only thing different is that I m using samba instead of 
nfs, but behaviour seems the same. On top of that we re encrypting the 
entire filesystems on this machine whicht now holds a total of 9 TB of 
attached storage.

In my observations those errors occure under the following conditions:

- using an smp system
- using applications which concurrently allocating memory in an 
aggressive manner
- freemem is at the lower limit given in vm.min_free_kbytes

Following numerous threats in mailinglists the has been some 
changes/patches for the most current kernels scoping these probs, 
however, if you are bound to a distribution kernel it may help to set 
the mentioned parameter

vm.min_free_kbytes

5 to 10 times bigger than given by default. At least for me it worked 
... no more oops, even under heavy load/backup etc.

---

Independently from this prob, can anyone confirm that there is a prob 
with concurrent allocating memory under load on linux smp systems?!

ciao
andi




       reply	other threads:[~2004-09-11  9:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2Ca3I-2kY-7@gated-at.bofh.it>
     [not found] ` <2Cdl9-4Pc-65@gated-at.bofh.it>
2004-09-11  9:21   ` ADH [this message]
     [not found] <20040908133954.GB390@unthought.net>
     [not found] ` <20040909074533.B3958243@wobbly.melbourne.sgi.com>
     [not found]   ` <413F823F.3020507@xfs.org>
2004-09-09  6:52     ` Major XFS problems Dave Chinner
2004-09-09  8:10       ` Andrew Morton
2004-09-08 15:24 Piszcz, Justin Michael
  -- strict thread matches above, loose matches on Subject: below --
2004-09-08 13:07 Piszcz, Justin Michael
2004-09-08 13:26 ` Jakob Oestergaard
2004-09-08 12:35 Jakob Oestergaard
2004-09-08 15:04 ` Anando Bhattacharya
2004-09-08 15:44   ` Jakob Oestergaard
2004-09-08 16:36     ` Greg Banks
2004-09-08 17:30       ` Jakob Oestergaard
2004-09-09  2:42         ` Greg Banks
2004-09-08 19:06       ` Bill Davidsen
2004-09-09  3:23         ` Greg Banks
2004-09-09 14:00       ` Jakob Oestergaard
2004-09-10  2:40         ` Greg Banks
2004-09-10  3:04           ` Kyle Moffett
2004-09-10  3:24             ` Greg Banks
2004-09-13  7:29         ` Jakob Oestergaard
2004-09-08 16:16 ` Jan-Frode Myklebust
2004-09-08 21:40 ` Nathan Scott
2004-09-08 23:22   ` Jakob Oestergaard
2004-09-08 23:42     ` Nathan Scott
2004-09-09 12:11       ` Jakob Oestergaard
2004-09-09 18:09         ` Chris Wedgwood
2004-09-11 11:39 ` Grzegorz Piotr Jaskiewicz
2004-09-11 13:03   ` Bjoern Brauel
2004-09-11 13:38   ` Anton Blanchard
2004-09-11 14:54     ` Miquel van Smoorenburg
2004-09-11 18:20     ` Grzegorz Piotr Jaskiewicz
2004-09-11 13:58 ` Clemens Schwaighofer

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=4142C3A1.1010005@adminsend.de \
    --to=swing@adminsend.de \
    --cc=linux-kernel@vger.kernel.org \
    /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