FS/XFS testing framework
 help / color / mirror / Atom feed
From: xiubli@redhat.com
To: fstests@vger.kernel.org
Cc: ddiss@suse.de, zlang@redhat.com, david@fromorbit.com,
	djwong@kernel.org, jlayton@kernel.org,
	ceph-devel@vger.kernel.org, lhenriques@suse.de,
	Xiubo Li <xiubli@redhat.com>
Subject: [PATCH] ceph/004: fix the ceph.quota.max_bytes values
Date: Mon, 29 Aug 2022 15:09:21 +0800	[thread overview]
Message-ID: <20220829070921.547074-1-xiubli@redhat.com> (raw)

From: Xiubo Li <xiubli@redhat.com>

Cephfs has required that the quota.max_bytes must be aligned to
4MB if greater than or equal to 4MB, otherwise must align to 4KB.

URL: https://tracker.ceph.com/issues/57321
Signed-off-by: Xiubo Li <xiubli@redhat.com>
---
 tests/ceph/004 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tests/ceph/004 b/tests/ceph/004
index dbca713e..124ed1bc 100755
--- a/tests/ceph/004
+++ b/tests/ceph/004
@@ -9,7 +9,7 @@
 #
 #    mkdir files limit
 #    truncate files/file -s 10G
-#    setfattr limit -n ceph.quota.max_bytes -v 1000000
+#    setfattr limit -n ceph.quota.max_bytes -v 1048576
 #    mv files limit/
 #
 # Because we're creating a new file and truncating it, we have Fx caps and thus
@@ -76,9 +76,9 @@ check_Fs_caps()
 }
 
 # set quota to 1m
-$SETFATTR_PROG -n ceph.quota.max_bytes -v 1000000 $dest
+$SETFATTR_PROG -n ceph.quota.max_bytes -v 1048576 $dest
 # set quota to 20g
-$SETFATTR_PROG -n ceph.quota.max_bytes -v 20000000000 $orig2
+$SETFATTR_PROG -n ceph.quota.max_bytes -v 21474836480 $orig2
 
 #
 # The following 2 testcases shall fail with either -EXDEV or -EDQUOT
-- 
2.36.0.rc1


             reply	other threads:[~2022-08-29  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  7:09 xiubli [this message]
2022-08-29 13:32 ` [PATCH] ceph/004: fix the ceph.quota.max_bytes values Luís Henriques

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=20220829070921.547074-1-xiubli@redhat.com \
    --to=xiubli@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=david@fromorbit.com \
    --cc=ddiss@suse.de \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=jlayton@kernel.org \
    --cc=lhenriques@suse.de \
    --cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox