linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: 2.6.38: Quota over NFS4
Date: Thu, 17 Mar 2011 14:32:47 +0100	[thread overview]
Message-ID: <20110317133247.GB6424@os.inf.tu-dresden.de> (raw)

Hello,

I'm seeing a problem with quotas in a system where the server running
2.6.38 exports an XFS filesystem via NFS4 to a client. The client kernel
version does not seem to play a role, checked with 2.6.38, 2.6.37 and
2.6.36. The following script and output show the problem:

#! /bin/sh

quota | grep home
du
cp /bin/ls x1
du
cat x1 > /dev/null
rm x1
du
quota | grep home

Output:

   homes:/home/ 8194720  9072000 9174400          403670  500000  550000        
0       .
96      .
0       .
   homes:/home/ 8194816  9072000 9174400          403671  500000  550000        


As can be seen the 96 kb are still accounted on the quota of the user.
Removing the 'cat' command from the script makes the quota be ok again
(original value). Also mounting via nfs3 does not exhibit it, same for running
the script on the nfs-server directly.

Client mount options are:
homes:/home/ /home nfs4 rw,nosuid,nodev,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=1.2.3.3,minorversion=0,local_lock=none,addr=1.2.3.4 0 0

Server mount options are:
/dev/mapper/vg-homefs /home xfs rw,nosuid,nodev,relatime,attr2,usrquota 0 0




Thanks,
Adam
-- 
Adam                 adam@os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/

             reply	other threads:[~2011-03-17 14:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 13:32 Adam Lackorzynski [this message]
2011-03-17 17:38 ` 2.6.38: Quota over NFS4 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
2011-03-24 17:51                                   ` J. Bruce Fields
2011-03-24 22:28                                     ` Adam Lackorzynski
2011-03-25  0:03                                       ` 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=20110317133247.GB6424@os.inf.tu-dresden.de \
    --to=adam@os.inf.tu-dresden.de \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).