linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Lord <lord@xfs.org>
To: Cahya Wirawan <cwirawan@email.archlab.tuwien.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4K stack kernel get Oops in Filesystem stress test
Date: Tue, 20 Jul 2004 07:04:49 -0500	[thread overview]
Message-ID: <40FD0A61.1040503@xfs.org> (raw)
In-Reply-To: <20040720114418.GH21918@email.archlab.tuwien.ac.at>

Cahya Wirawan wrote:
> Hi,
> I use vanila kernel 2.6.7 and 2.6.8-rc1 with 4K stack enabled,
> but if I execute the filesystem stress test from ltp.sf.net (linux test
> project) the machine always crash immediately. Or it will crash also after few
> hours if I do kernel compile test repeatedly. But if I use 8K stack,
> my server survive this filesystem stress test.
> Also my notebook get oops if I used 4k stack in kernel , but it crashed 
> after few minutes running the filesystem stress test (not immediately).
> My configuration is
> compaq proliant ML530/G2 , 2 processor intel 2.4Ghz, 1GB ram ,
> LVM1 volume with XFS filesystem.
> and here is the Oops message:


Don't use 4K stacks and XFS. What you hit here is a path where the
filesystem is getting full and it needs to free some reserved space
by flushing cached data which is using reserved extents. Reserved
extents do not yet have an on disk address and they include a
reservation for the worst case metadata usage. Flushing them will
get you room back.

As you can see, it is a pretty deep call stack, most of XFS is going
to work just fine with a 4K stack, but there are end cases like
this one which will just not fit.

Steve


  reply	other threads:[~2004-07-20 12:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 11:44 4K stack kernel get Oops in Filesystem stress test Cahya Wirawan
2004-07-20 12:04 ` Steve Lord [this message]
2004-07-20 14:39   ` Jeffrey E. Hundstad
2004-07-20 19:50     ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Adrian Bunk
2004-07-20 20:42       ` Chris Wedgwood
2004-07-20 20:50         ` Adrian Bunk
2004-07-20 20:58           ` Chris Wedgwood
2004-07-29  6:09       ` Nathan Scott
2004-07-29 11:42         ` Adrian Bunk
2004-07-29 11:46           ` Arjan van de Ven
2004-07-29 21:11             ` Adrian Bunk
2004-07-29 21:44               ` Chris Wedgwood
2004-07-29 22:30           ` [xfs-masters] " Nathan Scott
2004-08-01 19:02             ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL Adrian Bunk
2004-07-29 15:42         ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Mika Bostrom
2004-07-29 16:09           ` Zwane Mwaikambo
2004-07-29 16:36             ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS Mika Bostrom
2004-07-22  7:27     ` 4K stack kernel get Oops in Filesystem stress test Amon Ott
2004-07-29  2:14       ` Nathan Scott

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=40FD0A61.1040503@xfs.org \
    --to=lord@xfs.org \
    --cc=cwirawan@email.archlab.tuwien.ac.at \
    --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;
as well as URLs for NNTP newsgroup(s).