[PATCH 0/2] xfs: write back inodes during reclaim

Yann Dupont Yann.Dupont at univ-nantes.fr
Fri Apr 15 04:13:57 CDT 2011


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 at univ-nantes.fr




More information about the xfs mailing list