From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>, francois.valenduc@tvcablenet.be
Subject: Re: [Fwd: [xfs-masters] [Bug 11813] New: xfs filesystem exported via nfs don't work in 2.6.27.3]
Date: Thu, 23 Oct 2008 18:32:21 -0400 [thread overview]
Message-ID: <20081023223221.GA32629@infradead.org> (raw)
In-Reply-To: <4900F34C.2090205@sgi.com>
On Fri, Oct 24, 2008 at 07:57:32AM +1000, Mark Goodwin wrote:
> looks like we better do something urgently to fix this.
> Any suggestions Christoph?
Francois Valenduc wrote on Bugzilla:
> With kernel 2.6.27.3, it's impossible to use a xfs filesystem exported via
> NFS. I am using gentoo and I share a portage tree mounted on an xfs
> filesystem
> via NFS. Each time packages are fetched, the emerge process is blocked. It
> seems the problematic commit is the following:
>
> commit c068663ae65e507814545b59a8e2090f48a85613
I can't reproduce this, and intuitively this doesn't make sense.
The symptoms are the ones one would see due to the bug that is fixed by
this commit.
prev parent reply other threads:[~2008-10-23 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 21:57 [Fwd: [xfs-masters] [Bug 11813] New: xfs filesystem exported via nfs don't work in 2.6.27.3] Mark Goodwin
2008-10-23 22:32 ` Christoph Hellwig [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=20081023223221.GA32629@infradead.org \
--to=hch@infradead.org \
--cc=francois.valenduc@tvcablenet.be \
--cc=markgw@sgi.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