public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: panic on 4.20 server exporting xfs filesystem
Date: Tue, 3 Mar 2015 17:10:33 -0500	[thread overview]
Message-ID: <20150303221033.GB19439@fieldses.org> (raw)

I'm getting mysterious crashes on a server exporting an xfs filesystem.

Strangely, I've reproduced this on

	93aaa830fc17 "Merge tag 'xfs-pnfs-for-linus-3.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs

but haven't yet managed to reproduce on either of its parents
(24a52e412ef2 or 781355c6e5ae).  That might just be chance, I'll try
again.

I can also try a serial console or something, but for now I'm not
getting a lot of information about the crashes.

The filesystem in question isn't on a block device available to the
client, but I'm still seeing occasional GETLAYOUT and GETDEVICEINFO
calls; I suppose the client's getting that far, finding no devices it
can use, and giving up?

Sorry for the incomplete report, I'll pass along more when I have it.

--b.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2015-03-03 22:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 22:10 J. Bruce Fields [this message]
2015-03-03 22:44 ` panic on 4.20 server exporting xfs filesystem Dave Chinner
2015-03-04  2:08   ` J. Bruce Fields
2015-03-04  4:41     ` Dave Chinner
2015-03-05 13:19       ` Christoph Hellwig
2015-03-05 15:21         ` J. Bruce Fields
2015-03-08 13:08         ` Tom Haynes
2015-03-04 15:54     ` J. Bruce Fields
2015-03-04 22:09       ` Dave Chinner
2015-03-04 22:27         ` J. Bruce Fields
2015-03-04 22:45           ` Dave Chinner
2015-03-04 22:49             ` Eric Sandeen
2015-03-04 22:56               ` Dave Chinner
2015-03-05  4:08                 ` J. Bruce Fields
2015-03-05 13:17                   ` Christoph Hellwig
2015-03-05 15:01                     ` J. Bruce Fields
2015-03-05 17:02                       ` J. Bruce Fields
2015-03-05 20:47                         ` J. Bruce Fields
2015-03-05 20:59                           ` Dave Chinner
2015-03-06 20:47                             ` J. Bruce Fields
2015-03-19 17:27                               ` Christoph Hellwig
2015-03-19 18:47                                 ` J. Bruce Fields
2015-03-20  6:49                                   ` Christoph Hellwig
2015-03-08 15:30                           ` Christoph Hellwig
2015-03-09 19:45                             ` J. Bruce Fields
2015-03-20  4:06                     ` Kinglong Mee
2015-03-20  6:50                       ` Christoph Hellwig
2015-03-20  7:56                         ` [PATCH] NFSD: Fix infinite loop in nfsd4_cb_layout_fail() Kinglong Mee
2015-03-15 12:58 ` panic on 4.20 server exporting xfs filesystem Christoph Hellwig
2015-03-16 14:27   ` J. Bruce Fields
2015-03-17 10:30     ` Christoph Hellwig
2015-03-18 10:50     ` Christoph Hellwig

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=20150303221033.GB19439@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@lst.de \
    --cc=linux-nfs@vger.kernel.org \
    --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