From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] xfs: write back inodes during reclaim
Date: Fri, 15 Apr 2011 11:13:57 +0200 [thread overview]
Message-ID: <4DA80C55.7030903@univ-nantes.fr> (raw)
In-Reply-To: <20110415075440.GN21395@dastard>
Le 15/04/2011 09:54, Dave Chinner a écrit :
> {In future can you make sure you don't line wrap stack traces? they
> turn into an utter mess when being quoted if you wrap them}
>
woops, sorry :( I just copied/paste from our internal request tracker,
so the trace may have been mangled there.
> This, I'd say, has nothing to do with XFS - the system has taken a
> network interrupt and failed an allocation in bnx2 NIC driver. You
> chopped off the line that describes the actual allocation parameters
> that failed, so I can't really say why it failed...
>
once again sorry. I'm not used to send stack traces so often.
I'll try to send clean traces, only if you think it may have something
to do with xfs.
We have a lot of thoses traces, this particular one may not be the best
to describe the problem. My apologies.
...
> None right now - the patch is dead in the water right now because of
> lock inversion issues it causes. Even so, I doubt I'd be back
> porting it to any stable kernel without having anyone report that it
> is the root cause of their OOM problems.
>
ok
>> - Is mounting with noatime can alleviate the problem ?
> The problem that the patch I posted were supposed to fix, yes. The
> problem you are reporting here, most likely not.
ok,
thanks for your quick answer,
Regards,
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-04-15 9:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 6:19 [PATCH 0/2] xfs: write back inodes during reclaim Dave Chinner
2011-04-07 6:19 ` [PATCH 1/2] bdi: mark the bdi flusher busy when being forked Dave Chinner
2011-04-11 18:34 ` Christoph Hellwig
2011-04-13 19:29 ` Alex Elder
2011-04-07 6:19 ` [PATCH 2/2] xfs: kick inode writeback when low on memory Dave Chinner
2011-04-11 18:36 ` Christoph Hellwig
2011-04-11 21:14 ` Dave Chinner
2011-04-13 20:33 ` Alex Elder
2011-04-14 5:08 ` Dave Chinner
2011-04-15 8:09 ` Christoph Hellwig
2011-04-15 7:23 ` [PATCH 0/2] xfs: write back inodes during reclaim Yann Dupont
2011-04-15 7:54 ` Dave Chinner
2011-04-15 9:13 ` Yann Dupont [this message]
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=4DA80C55.7030903@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=david@fromorbit.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