From: Jakob Oestergaard <jakob@unthought.net>
To: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Major XFS problems...
Date: Wed, 8 Sep 2004 15:26:41 +0200 [thread overview]
Message-ID: <20040908132641.GA390@unthought.net> (raw)
In-Reply-To: <2E314DE03538984BA5634F12115B3A4E62EB0E@email1.mitretek.org>
On Wed, Sep 08, 2004 at 09:07:56AM -0400, Piszcz, Justin Michael wrote:
> This is a very well written+detailed bug report, have you tried writing
> the linux-xfs mailing list?
Thank you :)
No, I did not write the XFS list - but maybe I should...
I purposedly wrote directly to LKML to get the attention of a "broader
audience".
For example, the lowmem OOM problem may not be fixable by the XFS
developers alone (I don't know), and I've heard whisperings about the
debug.c:106 problem being related to knfsd changes in the 2.6 series
(don't know how credible that is either).
So, I thought, maybe if more people were made aware of this, the right
people would have a chance of figuring this out :)
--
/ jakob
next prev parent reply other threads:[~2004-09-08 14:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 13:07 Major XFS problems Piszcz, Justin Michael
2004-09-08 13:26 ` Jakob Oestergaard [this message]
[not found] <2Ca3I-2kY-7@gated-at.bofh.it>
[not found] ` <2Cdl9-4Pc-65@gated-at.bofh.it>
2004-09-11 9:21 ` ADH
[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 ` Dave Chinner
2004-09-09 8:10 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-09-08 15:24 Piszcz, Justin Michael
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=20040908132641.GA390@unthought.net \
--to=jakob@unthought.net \
--cc=justin.piszcz@mitretek.org \
--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