From: Eric Sandeen <sandeen@sandeen.net>
To: kevin@kevinjamieson.com
Cc: xfs@oss.sgi.com
Subject: Re: Oops at xfs_bmbt_get_startoff in SLES 10 2.6.16
Date: Tue, 21 Apr 2009 21:16:55 -0500 [thread overview]
Message-ID: <49EE7E17.8050006@sandeen.net> (raw)
In-Reply-To: <53630.24.80.224.145.1240361692.squirrel@squirrel.kevinjamieson.com>
Kevin Jamieson wrote:
> On Thu, March 12, 2009 4:13 pm, Kevin Jamieson wrote:
>> On Thu, March 12, 2009 12:23 pm, Eric Sandeen wrote:
>>
>>> For SLES that usually is the best route...
>>>
>>> However, http://oss.sgi.com/archives/xfs/2009-02/msg00220.html looks
>>> applicable... don't think it ever got merged though.
>>>
>>> perhaps you could test it?
>> Thanks, Eric. I will test Lachlan's patch on our system.
>
> To follow this up, since applying the patch from the above thread there
> have been no re-occurrences of the issue on our test servers over the past
> month.
And you hit it pretty reliably before, right? Sounds like we need to
give that a pretty strong eyeball and get it merged, perhaps.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-22 2:17 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 [this message]
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
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=49EE7E17.8050006@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox