From: Jan Kara <jack@suse.cz>
To: "Mainz, Roland" <R.Mainz@eckelmann.de>
Cc: Jan Kara <jack@suse.cz>, Richard Weinberger <richard@nod.at>,
Sascha Hauer <s.hauer@pengutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Jan Kara <jack@suse.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Implementing quota support on Linux without block device as backing store ? / was: RE: [PATCH 1/8] quota: Allow to pass mount path to quotactl
Date: Tue, 4 Feb 2020 17:07:03 +0100 [thread overview]
Message-ID: <20200204160703.GG2388@quack2.suse.cz> (raw)
In-Reply-To: <db98497119d542b88e0cfc76d9b0921b@eckelmann.de>
On Tue 04-02-20 15:07:31, Mainz, Roland wrote:
> Sascha Hauer wrote:
> > This patch introduces the Q_PATH flag to the quotactl cmd argument.
> > When given, the path given in the special argument to quotactl will be the
> > mount path where the filesystem is mounted, instead of a path to the block
> > device.
> > This is necessary for filesystems which do not have a block device as backing
> > store. Particularly this is done for upcoming UBIFS support.
>
> Just curious: Did you check how NFSv4 (also a filesystem without block
> device as backing store...) implemented quota support ? Maybe there is
> already a solution...
Well, NFS does not really implement quota support. It relies on the server
(i.e., a local filesystem on the server) for quota tracking and enforcement
and the NFS client just gets the EDQUOT error the server got from the
filesystem. And for quota querrying (e.g. quota(1) command) there is a
special sideband rpc protocol handled by the quota tools. With NFSv4 there
is some support in the protocol itself for quota reporting but in Linux
this is not really supported because it does not map well to how Linux does
quotas.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-02-04 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:07 Implementing quota support on Linux without block device as backing store ? / was: RE: [PATCH 1/8] quota: Allow to pass mount path to quotactl Mainz, Roland
2020-02-04 16:07 ` Jan Kara [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=20200204160703.GG2388@quack2.suse.cz \
--to=jack@suse.cz \
--cc=R.Mainz@eckelmann.de \
--cc=jack@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
/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).