All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Jamieson <kevin@kevinjamieson.com>
To: xfs@oss.sgi.com
Subject: Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16
Date: Wed, 22 Apr 2009 23:24:29 -0700	[thread overview]
Message-ID: <49F0099D.3060004@kevinjamieson.com> (raw)
In-Reply-To: <B32B0133-B835-4D31-B52A-364F607B9866@sgi.com>

Felix Blyakher wrote:

> But I could never reproduce the problem, even with Lachlan's test
> program.

I was not able to reproduce the problem with Lachlan's test program 
either (although I did not experiment much with the parameters).

> Kevin, any idea what kind of io load triggered this problem?

The workload consisted of predominantly (98%) 2-3MB file ingests through 
an NFS share, with a a few (2%) 1GB file ingests, where the issue seemed 
to trigger on the larger files.

Kevin

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

  parent reply	other threads:[~2009-04-23  6:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 18:50 Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16 Kevin Jamieson
2009-03-12 19:23 ` Eric Sandeen
2009-03-12 23:13   ` Kevin Jamieson
2009-04-22  0:54     ` Kevin Jamieson
2009-04-22  2:16       ` Eric Sandeen
2009-04-22  2:31         ` Felix Blyakher
2009-04-22  2:32           ` Eric Sandeen
2009-04-22  2:35             ` Felix Blyakher
2009-04-22  2:38               ` Eric Sandeen
2009-04-23  6:24           ` Kevin Jamieson [this message]
2009-04-23  6:18         ` Kevin Jamieson
     [not found] <1416563271.242851240369384712.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-04-22  3:06 ` Lachlan McIlroy
2009-04-23  9:47   ` Christoph Hellwig
2009-04-24  2:43     ` Lachlan McIlroy

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=49F0099D.3060004@kevinjamieson.com \
    --to=kevin@kevinjamieson.com \
    --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.