From: Jan Kara <jack@suse.cz>
To: Yuanliang Wang <yuanliang.wyl@alibaba-inc.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
"adilger.kernel" <adilger.kernel@dilger.ca>,
pkuelelixi <pkuelelixi@gmail.com>, jack <jack@suse.cz>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 回复：ext4, quota, projectid: limits without capablity
Date: Wed, 10 Jan 2018 12:59:26 +0100 [thread overview]
Message-ID: <20180110115926.tk6bri37bdjhipc2@quack2.suse.cz> (raw)
In-Reply-To: <0dc571a8-e1b2-4247-9e9d-df02c0b0d7c6.yuanliang.wyl@alibaba-inc.com>
Hello Wang!
On Wed 10-01-18 19:01:03, Yuanliang Wang wrote:
> Thank you for your enthusiastic response
>
> the reason is :
> 1、I saw
> that ignore_hardlimit allows root to exceed the limit，so should projid
> be consistent ?
Generally, it should be consistent. ignore_hardlimit is a different thing -
you want root to be able to exceed storage space limit but you don't want
root to be able to make information inconsistent...
> 2、
> In our scenario we will use hardlink to share data between container and host, and between containers
>
> +------------------+
> | |
> | |
> +-------------+ | |
> | | | |
> | | | container |
> | +--------------> | |
> | | | file A |
> | | | |
> | | | |
> | | | |
> | | +------------------+
> | |
> | |
> | | +------------------+
> | | | |
> | | | |
> | | | |
> | | | |
> | | | container |
> | host file A +---------------> | |
> | | | file A |
> | | | |
> | | | |
> | | | |
> | | | |
> | | +------------------+
> | |
> | | +------------------+
> | | | |
> | | | |
> | | | |
> | | | |
> | +-------------> | container |
> | | | |
> | | | |
> | | | file A |
> | | | |
> +-------------+ | |
> | |
> +------------------+
I see but then which project ID does the 'file A' have? Project ID used for
neither of the containers is logical... Maybe the file is accessible only
read-only in your setup and so you don't care much about quotas for that
particular files but still it may be confusing that the file is not
accounted to the quota of each particular container. That's the reason why
project ID consistence is enforced.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2018-01-10 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c18ff577-be92-40ea-93ae-4401ce2107da.yuanliang.wyl@alibaba-inc.com>
2018-01-05 19:20 ` ext4, quota, projectid: limits without capablity Theodore Ts'o
[not found] ` <0dc571a8-e1b2-4247-9e9d-df02c0b0d7c6.yuanliang.wyl@alibaba-inc.com>
2018-01-10 11:59 ` 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=20180110115926.tk6bri37bdjhipc2@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pkuelelixi@gmail.com \
--cc=tytso@mit.edu \
--cc=yuanliang.wyl@alibaba-inc.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;
as well as URLs for NNTP newsgroup(s).