From: "Luís Henriques" <lhenriques@suse.de>
To: Jeff Layton <jlayton@kernel.org>, Xiubo Li <xiubli@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
"Luís Henriques" <lhenriques@suse.de>
Subject: [RFC PATCH v3 3/4] ceph: update documentation regarding snapshot naming limitations
Date: Thu, 17 Mar 2022 15:45:20 +0000 [thread overview]
Message-ID: <20220317154521.6615-4-lhenriques@suse.de> (raw)
In-Reply-To: <20220317154521.6615-1-lhenriques@suse.de>
Signed-off-by: Luís Henriques <lhenriques@suse.de>
---
Documentation/filesystems/ceph.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/filesystems/ceph.rst b/Documentation/filesystems/ceph.rst
index 4942e018db85..d487cabe792d 100644
--- a/Documentation/filesystems/ceph.rst
+++ b/Documentation/filesystems/ceph.rst
@@ -57,6 +57,16 @@ a snapshot on any subdirectory (and its nested contents) in the
system. Snapshot creation and deletion are as simple as 'mkdir
.snap/foo' and 'rmdir .snap/foo'.
+Snapshot names have two limitations:
+
+* They can not start with an underscore ('_'), as these names are reserved
+ for internal usage by the MDS.
+* They can not exceed 240 characters in size. This is because the MDS makes
+ use of long snapshot names internally, which follow the format:
+ `_<SNAPSHOT-NAME>_<INODE-NUMBER>`. Since filenames in general can't have
+ more than 255 characters, and `<node-id>` takes 13 characters, the long
+ snapshot names can take as much as 255 - 1 - 1 - 13 = 240.
+
Ceph also provides some recursive accounting on directories for nested
files and bytes. That is, a 'getfattr -d foo' on any directory in the
system will reveal the total number of nested regular files and
next prev parent reply other threads:[~2022-03-17 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 15:45 [RFC PATCH v3 0/4] ceph: add support for snapshot names encryption Luís Henriques
2022-03-17 15:45 ` [RFC PATCH v3 1/4] ceph: add support for encrypted snapshot names Luís Henriques
2022-03-17 15:45 ` [RFC PATCH v3 2/4] ceph: handle encrypted snapshot names in subdirectories Luís Henriques
2022-03-18 4:57 ` Xiubo Li
2022-03-18 9:57 ` Jeff Layton
2022-03-18 11:19 ` Xiubo Li
2022-03-18 10:53 ` Luís Henriques
2022-03-18 11:28 ` Xiubo Li
2022-03-18 11:49 ` Luís Henriques
2022-03-17 15:45 ` Luís Henriques [this message]
2022-03-17 15:45 ` [RFC PATCH v3 4/4] ceph: replace base64url by the encoding used for mailbox names Luís Henriques
2022-03-18 8:32 ` Xiubo Li
2022-03-18 11:01 ` 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=20220317154521.6615-4-lhenriques@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiubli@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