From: Chao Yu <yuchao0@huawei.com>
To: <guaneryu@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.orga, fstests@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 3/3] common/rc: check quota sysfile feature for f2fs
Date: Tue, 23 Jul 2019 17:25:29 +0800 [thread overview]
Message-ID: <20190723092529.112426-3-yuchao0@huawei.com> (raw)
In-Reply-To: <20190723092529.112426-1-yuchao0@huawei.com>
In _require_prjquota(), f2fs missed to check whether we have enabled
quota sysfile feature in the image, add it.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
---
common/quota | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/quota b/common/quota
index 9af280a2..3f46eb19 100644
--- a/common/quota
+++ b/common/quota
@@ -80,6 +80,8 @@ _require_prjquota()
if [ "$FSTYP" == "f2fs" ]; then
dump.f2fs $_dev 2>&1 | grep -qw project_quota
[ $? -ne 0 ] && _notrun "Project quota not enabled in this device $_dev"
+ dump.f2fs $_dev 2>&1 | grep -qw quota_ino
+ [ $? -ne 0 ] && _notrun "quota sysfile not enabled in this device $_dev"
cat /sys/fs/f2fs/features/project_quota | grep -qw supported
[ $? -ne 0 ] && _notrun "Installed kernel does not support project quotas"
return
--
2.18.0.rc1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-07-23 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 9:25 [f2fs-dev] [PATCH 1/3] generic/38[3456]: adjust to check prjquota before mount Chao Yu
2019-07-23 9:25 ` [f2fs-dev] [PATCH 2/3] common/quota: support f2fs in _require_quota() and _check_quota_usage() Chao Yu
2019-07-23 9:25 ` Chao Yu [this message]
2019-07-28 9:51 ` [f2fs-dev] [PATCH 1/3] generic/38[3456]: adjust to check prjquota before mount Eryu Guan
2019-07-29 11:43 ` Chao Yu
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=20190723092529.112426-3-yuchao0@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.orga \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).