public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mario Becroft <mb@gem.win.co.nz>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error when NFS client accesses nonexistent inode
Date: Thu, 1 Jan 2009 12:37:56 -0500	[thread overview]
Message-ID: <20090101173756.GA31126@infradead.org> (raw)
In-Reply-To: <20090101171409.GA18020@infradead.org>

This should cure your shutdowns on a 2.6.27-ish codebase:



Index: btrfs-unstable/fs/xfs/linux-2.6/xfs_export.c
===================================================================
--- btrfs-unstable.orig/fs/xfs/linux-2.6/xfs_export.c	2009-01-01 18:34:39.868671500 +0100
+++ btrfs-unstable/fs/xfs/linux-2.6/xfs_export.c	2009-01-01 18:35:37.224782654 +0100
@@ -127,8 +127,8 @@ xfs_nfs_get_inode(
 	if (ino == 0)
 		return ERR_PTR(-ESTALE);
 
-	error = xfs_iget(mp, NULL, ino, 0, XFS_ILOCK_SHARED, &ip, 0);
+	error = xfs_iget(mp, NULL, ino, XFS_IGET_BULKSTAT, XFS_ILOCK_SHARED, &ip, 0);
 		return ERR_PTR(-error);
 	if (!ip)
 		return ERR_PTR(-EIO);

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

  reply	other threads:[~2009-01-01 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 14:09 XFS internal error when NFS client accesses nonexistent inode Mario Becroft
2009-01-01 17:14 ` Christoph Hellwig
2009-01-01 17:37   ` Christoph Hellwig [this message]
2009-01-01 19:00   ` Christoph Hellwig
2009-01-01 23:15     ` Mario Becroft
2009-01-01 23:20       ` Christoph Hellwig
2009-01-01 17:17 ` Feature requests, was " 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=20090101173756.GA31126@infradead.org \
    --to=hch@infradead.org \
    --cc=mb@gem.win.co.nz \
    --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