From: Xiubo Li <xiubli@redhat.com>
To: "Luís Henriques" <lhenriques@suse.de>,
"Jeff Layton" <jlayton@kernel.org>,
"Ilya Dryomov" <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 3/3] ceph: update documentation regarding snapshot naming limitations
Date: Wed, 16 Mar 2022 08:48:30 +0800 [thread overview]
Message-ID: <db0eb19c-7ad9-8cc1-b0da-59b59c308cc1@redhat.com> (raw)
In-Reply-To: <20220315161959.19453-4-lhenriques@suse.de>
On 3/16/22 12:19 AM, Luís Henriques wrote:
> 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
>
LGTM.
Reviewed-by: Xiubo Li <xiubli@redhat.com>
next prev parent reply other threads:[~2022-03-16 0:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 16:19 [RFC PATCH v2 0/3] ceph: add support for snapshot names encryption Luís Henriques
2022-03-15 16:19 ` [RFC PATCH v2 1/3] ceph: add support for encrypted snapshot names Luís Henriques
2022-03-16 0:07 ` Xiubo Li
2022-03-15 16:19 ` [RFC PATCH v2 2/3] ceph: add support for handling " Luís Henriques
2022-03-16 0:47 ` Xiubo Li
2022-03-16 11:00 ` Luís Henriques
2022-03-15 16:19 ` [RFC PATCH v2 3/3] ceph: update documentation regarding snapshot naming limitations Luís Henriques
2022-03-16 0:48 ` Xiubo Li [this message]
2022-03-17 5:27 ` [RFC PATCH v2 0/3] ceph: add support for snapshot names encryption Xiubo Li
2022-03-17 10:01 ` Jeff Layton
2022-03-17 10:52 ` Xiubo Li
2022-03-17 11:11 ` Luís Henriques
2022-03-17 11:28 ` Xiubo Li
2022-03-17 12:01 ` Jeff Layton
2022-03-17 12:31 ` Xiubo Li
2022-03-17 12:41 ` Jeff Layton
2022-03-17 12:44 ` Xiubo Li
2022-03-17 15:59 ` Luís Henriques
2022-03-17 10:14 ` Luís Henriques
2022-03-17 11:02 ` Xiubo Li
2022-03-17 11:22 ` Xiubo Li
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=db0eb19c-7ad9-8cc1-b0da-59b59c308cc1@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®