All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <lhenriques@suse.com>
To: ceph-devel@vger.kernel.org
Cc: "Yan, Zheng" <zyan@redhat.com>, Luis Henriques <lhenriques@suse.com>
Subject: [RFC PATCH v2 0/1] quota: report root dir quota usage in statfs
Date: Wed, 31 Jan 2018 10:53:12 +0000	[thread overview]
Message-ID: <20180131105313.24802-1-lhenriques@suse.com> (raw)

Following this email I'm sending a patch that modifies the statfs
behaviour in cephfs kernel client so that, by default, it shows the
quota statistics for the root directory instead of the overall
filesystem usage.

I'm sending this patch as an RFC because:

 * I'm not sure people really want to have this behaviour -- this is the
   default for the ceph-fuse client, so I just wanted to have a similar
   behaviour in the kernel client.
 * Showing quota usage by default may not be the correct option,
   although (again!) this is what the ceph-fuse client does.

Anyway, there's also a new mount option ('noquotadf') to revert to the
old statfs even if the root dir has max_bytes set.

Just for reference, this statfs behaviour was added to the ceph-fuse
client by commit b6d2b6d1a519 ("client: report root's quota in
statfs").

** Changes since v1 **

- Rework after review from Yan, Zheng:
  * Added '()' to expression
  * Added an extra 'quotadf' mount option

Luis Henriques (1):
  quota: report root dir quota usage in statfs

 Documentation/filesystems/ceph.txt |  4 +++
 fs/ceph/quota.c                    | 56 ++++++++++++++++++++++++++++++++++++++
 fs/ceph/super.c                    | 29 ++++++++++++++++++--
 fs/ceph/super.h                    |  3 ++
 4 files changed, 89 insertions(+), 3 deletions(-)


             reply	other threads:[~2018-01-31 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 10:53 Luis Henriques [this message]
2018-01-31 10:53 ` [RFC PATCH v2 1/1] quota: report root dir quota usage in statfs Luis Henriques
2018-02-01  3:55   ` Yan, Zheng

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=20180131105313.24802-1-lhenriques@suse.com \
    --to=lhenriques@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=zyan@redhat.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.