From: Christoph Hellwig <hch@infradead.org>
To: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.38: Quota over NFS4
Date: Thu, 24 Mar 2011 13:17:05 -0400 [thread overview]
Message-ID: <20110324171704.GA1784@infradead.org> (raw)
In-Reply-To: <20110323223017.GA5177@os.inf.tu-dresden.de>
On Wed, Mar 23, 2011 at 11:30:17PM +0100, Adam Lackorzynski wrote:
> I probably mistyped something and thus bisected again:
maybe this is just a symptom. When was the nfs4 code converted
to just use a single open struct file, and what are the lifetime
rules for it? It would easily be that a long alive file might
make XFS keep persistent preallocations longer or similar issues.
Adam, can you create a loop filesystem with ext3 or something else
on it and see if the problem is XFS-specific?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.38: Quota over NFS4
Date: Thu, 24 Mar 2011 13:17:05 -0400 [thread overview]
Message-ID: <20110324171704.GA1784@infradead.org> (raw)
In-Reply-To: <20110323223017.GA5177@os.inf.tu-dresden.de>
On Wed, Mar 23, 2011 at 11:30:17PM +0100, Adam Lackorzynski wrote:
> I probably mistyped something and thus bisected again:
maybe this is just a symptom. When was the nfs4 code converted
to just use a single open struct file, and what are the lifetime
rules for it? It would easily be that a long alive file might
make XFS keep persistent preallocations longer or similar issues.
Adam, can you create a loop filesystem with ext3 or something else
on it and see if the problem is XFS-specific?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-24 17:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:32 2.6.38: Quota over NFS4 Adam Lackorzynski
2011-03-17 17:38 ` J. Bruce Fields
2011-03-17 21:33 ` Adam Lackorzynski
2011-03-17 22:27 ` J. Bruce Fields
2011-03-17 22:59 ` Adam Lackorzynski
2011-03-17 23:03 ` J. Bruce Fields
2011-03-17 23:16 ` Adam Lackorzynski
[not found] ` <20110320172758.GK11929@os.inf.tu-dresden.de>
[not found] ` <20110320212633.GA26036@fieldses.org>
[not found] ` <20110320213111.GO11929@os.inf.tu-dresden.de>
[not found] ` <20110320214316.GB26036@fieldses.org>
[not found] ` <20110321184043.GC4992@os.inf.tu-dresden.de>
[not found] ` <20110321222301.GB472@fieldses.org>
[not found] ` <20110322221305.GA5857@os.inf.tu-dresden.de>
[not found] ` <20110323150328.GD23418@fieldses.org>
[not found] ` <20110323174052.GE5005@os.inf.tu-dresden.de>
2011-03-23 19:06 ` J. Bruce Fields
2011-03-23 22:30 ` Adam Lackorzynski
2011-03-24 17:17 ` Christoph Hellwig [this message]
2011-03-24 17:17 ` Christoph Hellwig
2011-03-24 17:51 ` J. Bruce Fields
2011-03-24 17:51 ` J. Bruce Fields
2011-03-24 22:28 ` Adam Lackorzynski
2011-03-24 22:28 ` Adam Lackorzynski
2011-03-25 0:03 ` J. Bruce Fields
2011-03-25 0:03 ` J. Bruce Fields
2011-04-22 19:31 ` J. Bruce Fields
2011-04-22 19:31 ` J. Bruce Fields
2011-03-20 19:49 ` Maciej Rutecki
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=20110324171704.GA1784@infradead.org \
--to=hch@infradead.org \
--cc=adam@os.inf.tu-dresden.de \
--cc=bfields@fieldses.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.