From: Dave Chinner <david@fromorbit.com>
To: Gregory Machin <gdm@linuxpro.co.za>
Cc: xfs@oss.sgi.com
Subject: Re: xf kernel trace , what is the cause ?
Date: Wed, 7 May 2014 08:49:40 +1000 [thread overview]
Message-ID: <20140506224940.GP5421@dastard> (raw)
In-Reply-To: <CAJzjPK=YF3=xx5dSGzw4S44Nf01o6d1tcqiiofE4m-nuWdOKTQ@mail.gmail.com>
On Wed, May 07, 2014 at 09:18:46AM +1200, Gregory Machin wrote:
> Hi.
>
> I have a file server that has had 2 xfs Kernel trace dumps about 2 weeks
> apart.
>
> The RAID 60 data store is mounted as /home with xfs as the file system. The
> /home space is shares via NFS export and CIFS share. At the time of
> the Trace dumps NFS access hangs and crashed users sessions on the client
> side. The output of the last traces is below.
>
> Can you advise as to the cause of this dump and possible resolution ?
Commit 2732036 ("xfs: xfs_remove deadlocks due to inverted AGF vs AGI
lock ordering") fixed it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-05-06 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 21:18 xf kernel trace , what is the cause ? Gregory Machin
2014-05-06 22:49 ` Dave Chinner [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=20140506224940.GP5421@dastard \
--to=david@fromorbit.com \
--cc=gdm@linuxpro.co.za \
--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