sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget$/translations/zh_CN/filesystems/cephmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/zh_TW/filesystems/cephmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/it_IT/filesystems/cephmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/ja_JP/filesystems/cephmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/ko_KR/filesystems/cephmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget$/translations/sp_SP/filesystems/cephmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhh>/var/lib/git/docbuild/linux/Documentation/filesystems/ceph.rsthKubhsection)}(hhh](htitle)}(hCeph Distributed File Systemh]hCeph Distributed File System}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(hmCeph is a distributed network file system designed to provide good performance, reliability, and scalability.h]hmCeph is a distributed network file system designed to provide good performance, reliability, and scalability.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hBasic features include:h]hBasic features include:}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh block_quote)}(hXR* POSIX semantics * Seamless scaling from 1 to many thousands of nodes * High availability and reliability. No single point of failure. * N-way replication of data across storage nodes * Fast recovery from node failures * Automatic rebalancing of data on node addition/removal * Easy deployment: most FS components are userspace daemons h]h bullet_list)}(hhh](h list_item)}(hPOSIX semanticsh]h)}(hhh]hPOSIX semantics}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhubah}(h]h ]h"]h$]h&]uh1hhhubh)}(h2Seamless scaling from 1 to many thousands of nodesh]h)}(hj h]h2Seamless scaling from 1 to many thousands of nodes}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hj ubah}(h]h ]h"]h$]h&]uh1hhhubh)}(h?High availability and reliability. No single point of failure.h]h)}(hj$h]h?High availability and reliability. No single point of failure.}(hj&hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj"ubah}(h]h ]h"]h$]h&]uh1hhhubh)}(h.N-way replication of data across storage nodesh]h)}(hj;h]h.N-way replication of data across storage nodes}(hj=hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj9ubah}(h]h ]h"]h$]h&]uh1hhhubh)}(h Fast recovery from node failuresh]h)}(hjRh]h Fast recovery from node failures}(hjThhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjPubah}(h]h ]h"]h$]h&]uh1hhhubh)}(h6Automatic rebalancing of data on node addition/removalh]h)}(hjih]h6Automatic rebalancing of data on node addition/removal}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjgubah}(h]h ]h"]h$]h&]uh1hhhubh)}(h:Easy deployment: most FS components are userspace daemons h]h)}(h9Easy deployment: most FS components are userspace daemonsh]h9Easy deployment: most FS components are userspace daemons}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj~ubah}(h]h ]h"]h$]h&]uh1hhhubeh}(h]h ]h"]h$]h&]bullet*uh1hhhhK hhubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hAlso,h]hAlso,}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hb* Flexible snapshots (on any directory) * Recursive accounting (nested files, directories, bytes) h]h)}(hhh](h)}(h%Flexible snapshots (on any directory)h]h)}(hjh]h%Flexible snapshots (on any directory)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubh)}(h8Recursive accounting (nested files, directories, bytes) h]h)}(h7Recursive accounting (nested files, directories, bytes)h]h7Recursive accounting (nested files, directories, bytes)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubeh}(h]h ]h"]h$]h&]jjuh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hXIn contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely on symmetric access by all clients to shared block devices, Ceph separates data and metadata management into independent server clusters, similar to Lustre. Unlike Lustre, however, metadata and storage nodes run entirely as user space daemons. File data is striped across storage nodes in large chunks to distribute workload and facilitate high throughputs. When storage nodes fail, data is re-replicated in a distributed fashion by the storage nodes themselves (with some minimal coordination from a cluster monitor), making the system extremely efficient and scalable.h]hXIn contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely on symmetric access by all clients to shared block devices, Ceph separates data and metadata management into independent server clusters, similar to Lustre. Unlike Lustre, however, metadata and storage nodes run entirely as user space daemons. File data is striped across storage nodes in large chunks to distribute workload and facilitate high throughputs. When storage nodes fail, data is re-replicated in a distributed fashion by the storage nodes themselves (with some minimal coordination from a cluster monitor), making the system extremely efficient and scalable.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hXMetadata servers effectively form a large, consistent, distributed in-memory cache above the file namespace that is extremely scalable, dynamically redistributes metadata in response to workload changes, and can tolerate arbitrary (well, non-Byzantine) node failures. The metadata server takes a somewhat unconventional approach to metadata storage to significantly improve performance for common workloads. In particular, inodes with only a single link are embedded in directories, allowing entire directories of dentries and inodes to be loaded into its cache with a single I/O operation. The contents of extremely large directories can be fragmented and managed by independent metadata servers, allowing scalable concurrent access.h]hXMetadata servers effectively form a large, consistent, distributed in-memory cache above the file namespace that is extremely scalable, dynamically redistributes metadata in response to workload changes, and can tolerate arbitrary (well, non-Byzantine) node failures. The metadata server takes a somewhat unconventional approach to metadata storage to significantly improve performance for common workloads. In particular, inodes with only a single link are embedded in directories, allowing entire directories of dentries and inodes to be loaded into its cache with a single I/O operation. The contents of extremely large directories can be fragmented and managed by independent metadata servers, allowing scalable concurrent access.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK$hhhhubh)}(hXnThe system offers automatic data rebalancing/migration when scaling from a small cluster of just a few nodes to many hundreds, without requiring an administrator carve the data set into static volumes or go through the tedious process of migrating data between servers. When the file system approaches full, new nodes can be easily added and things will "just work."h]hXrThe system offers automatic data rebalancing/migration when scaling from a small cluster of just a few nodes to many hundreds, without requiring an administrator carve the data set into static volumes or go through the tedious process of migrating data between servers. When the file system approaches full, new nodes can be easily added and things will “just work.”}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK0hhhhubh)}(hCeph includes flexible snapshot mechanism that allows a user to create 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'.h]hCeph includes flexible snapshot mechanism that allows a user to create 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’.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK7hhhhubh)}(h$Snapshot names have two limitations:h]h$Snapshot names have two limitations:}(hj,hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj=ubah}(h]h ]h"]h$]h&]uh1hhj:hhhhhNubh)}(hXXThey can not exceed 240 characters in size. This is because the MDS makes use of long snapshot names internally, which follow the format: `__`. Since filenames in general can't have more than 255 characters, and `` takes 13 characters, the long snapshot names can take as much as 255 - 1 - 1 - 13 = 240. h]h)}(hXWThey can not exceed 240 characters in size. This is because the MDS makes use of long snapshot names internally, which follow the format: `__`. Since filenames in general can't have more than 255 characters, and `` takes 13 characters, the long snapshot names can take as much as 255 - 1 - 1 - 13 = 240.h](hThey can not exceed 240 characters in size. This is because the MDS makes use of long snapshot names internally, which follow the format: }(hjYhhhNhNubhtitle_reference)}(h!`__`h]h__}(hjchhhNhNubah}(h]h ]h"]h$]h&]uh1jahjYubhI. Since filenames in general can’t have more than 255 characters, and }(hjYhhhNhNubjb)}(h ``h]h }(hjuhhhNhNubah}(h]h ]h"]h$]h&]uh1jahjYubhY takes 13 characters, the long snapshot names can take as much as 255 - 1 - 1 - 13 = 240.}(hjYhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK@hjUubah}(h]h ]h"]h$]h&]uh1hhj:hhhhhNubeh}(h]h ]h"]h$]h&]jjuh1hhhhK>hhhhubh)}(hsCeph also provides some recursive accounting on directories for nested files and bytes. You can run the commands::h]hrCeph also provides some recursive accounting on directories for nested files and bytes. You can run the commands:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKFhhhhubh literal_block)}(hKgetfattr -n ceph.dir.rfiles /some/dir getfattr -n ceph.dir.rbytes /some/dirh]hKgetfattr -n ceph.dir.rfiles /some/dir getfattr -n ceph.dir.rbytes /some/dir}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhKIhhhhubh)}(hto get the total number of nested files and their combined size, respectively. This makes the identification of large disk space consumers relatively quick, as no 'du' or similar recursive scan of the file system is required.h]hto get the total number of nested files and their combined size, respectively. This makes the identification of large disk space consumers relatively quick, as no ‘du’ or similar recursive scan of the file system is required.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKLhhhhubh)}(hX'Finally, Ceph also allows quotas to be set on any directory in the system. The quota can restrict the number of bytes or the number of files stored beneath that point in the directory hierarchy. Quotas can be set using extended attributes 'ceph.quota.max_files' and 'ceph.quota.max_bytes', eg::h]hX.Finally, Ceph also allows quotas to be set on any directory in the system. The quota can restrict the number of bytes or the number of files stored beneath that point in the directory hierarchy. Quotas can be set using extended attributes ‘ceph.quota.max_files’ and ‘ceph.quota.max_bytes’, eg:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKPhhhhubj)}(hbsetfattr -n ceph.quota.max_bytes -v 100000000 /some/dir getfattr -n ceph.quota.max_bytes /some/dirh]hbsetfattr -n ceph.quota.max_bytes -v 100000000 /some/dir getfattr -n ceph.quota.max_bytes /some/dir}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhKUhhhhubh)}(hXA limitation of the current quotas implementation is that it relies on the cooperation of the client mounting the file system to stop writers when a limit is reached. A modified or adversarial client cannot be prevented from writing as much data as it needs.h]hXA limitation of the current quotas implementation is that it relies on the cooperation of the client mounting the file system to stop writers when a limit is reached. A modified or adversarial client cannot be prevented from writing as much data as it needs.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKXhhhhubh)}(hhh](h)}(h Mount Syntaxh]h Mount Syntax}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK^ubh)}(hThe basic mount syntax is::h]hThe basic mount syntax is:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK`hjhhubj)}(hY# mount -t ceph user@fsid.fs_name=/[subdir] mnt -o mon_addr=monip1[:port][/monip2[:port]]h]hY# mount -t ceph user@fsid.fs_name=/[subdir] mnt -o mon_addr=monip1[:port][/monip2[:port]]}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhKbhjhhubh)}(hXYou only need to specify a single monitor, as the client will get the full list when it connects. (However, if the monitor you specify happens to be down, the mount won't succeed.) The port can be left off if the monitor is using the default. So if the monitor is at 1.2.3.4::h]hXYou only need to specify a single monitor, as the client will get the full list when it connects. (However, if the monitor you specify happens to be down, the mount won’t succeed.) The port can be left off if the monitor is using the default. So if the monitor is at 1.2.3.4:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKdhjhhubj)}(hd# mount -t ceph cephuser@07fe3187-00d9-42a3-814b-72a4d5e7d5be.cephfs=/ /mnt/ceph -o mon_addr=1.2.3.4h]hd# mount -t ceph cephuser@07fe3187-00d9-42a3-814b-72a4d5e7d5be.cephfs=/ /mnt/ceph -o mon_addr=1.2.3.4}hj*sbah}(h]h ]h"]h$]h&]hhuh1jhhhKjhjhhubh)}(his sufficient. If /sbin/mount.ceph is installed, a hostname can be used instead of an IP address and the cluster FSID can be left out (as the mount helper will fill it in by reading the ceph configuration file)::h]his sufficient. If /sbin/mount.ceph is installed, a hostname can be used instead of an IP address and the cluster FSID can be left out (as the mount helper will fill it in by reading the ceph configuration file):}(hj8hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKlhjhhubj)}(h@# mount -t ceph cephuser@cephfs=/ /mnt/ceph -o mon_addr=mon-addrh]h@# mount -t ceph cephuser@cephfs=/ /mnt/ceph -o mon_addr=mon-addr}hjFsbah}(h]h ]h"]h$]h&]hhuh1jhhhKqhjhhubh)}(hXMultiple monitor addresses can be passed by separating each address with a slash (`/`)::h](hRMultiple monitor addresses can be passed by separating each address with a slash (}(hjThhhNhNubjb)}(h`/`h]h/}(hj\hhhNhNubah}(h]h ]h"]h$]h&]uh1jahjTubh):}(hjThhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKshjhhubj)}(hS# mount -t ceph cephuser@cephfs=/ /mnt/ceph -o mon_addr=192.168.1.100/192.168.1.101h]hS# mount -t ceph cephuser@cephfs=/ /mnt/ceph -o mon_addr=192.168.1.100/192.168.1.101}hjtsbah}(h]h ]h"]h$]h&]hhuh1jhhhKuhjhhubh)}(hWhen using the mount helper, monitor address can be read from ceph configuration file if available. Note that, the cluster FSID (passed as part of the device string) is validated by checking it with the FSID reported by the monitor.h]hWhen using the mount helper, monitor address can be read from ceph configuration file if available. Note that, the cluster FSID (passed as part of the device string) is validated by checking it with the FSID reported by the monitor.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKwhjhhubeh}(h] mount-syntaxah ]h"] mount syntaxah$]h&]uh1hhhhhhhhK^ubh)}(hhh](h)}(h Mount Optionsh]h Mount Options}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK}ubh)}(hX mon_addr=ip_address[:port][/ip_address[:port]] Monitor address to the cluster. This is used to bootstrap the connection to the cluster. Once connection is established, the monitor addresses in the monitor map are followed. fsid=cluster-id FSID of the cluster (from `ceph fsid` command). ip=A.B.C.D[:N] Specify the IP and/or port the client should bind to locally. There is normally not much reason to do this. If the IP is not specified, the client's IP address is determined by looking at the address its connection to the monitor originates from. wsize=X Specify the maximum write size in bytes. Default: 64 MB. rsize=X Specify the maximum read size in bytes. Default: 64 MB. rasize=X Specify the maximum readahead size in bytes. Default: 8 MB. mount_timeout=X Specify the timeout value for mount (in seconds), in the case of a non-responsive Ceph file system. The default is 60 seconds. caps_max=X Specify the maximum number of caps to hold. Unused caps are released when number of caps exceeds the limit. The default is 0 (no limit) rbytes When stat() is called on a directory, set st_size to 'rbytes', the summation of file sizes over all files nested beneath that directory. This is the default. norbytes When stat() is called on a directory, set st_size to the number of entries in that directory. nocrc Disable CRC32C calculation for data writes. If set, the storage node must rely on TCP's error correction to detect data corruption in the data payload. dcache Use the dcache contents to perform negative lookups and readdir when the client has the entire directory contents in its cache. (This does not change correctness; the client uses cached metadata only when a lease or capability ensures it is valid.) nodcache Do not use the dcache as above. This avoids a significant amount of complex code, sacrificing performance without affecting correctness, and is useful for tracking down bugs. noasyncreaddir Do not use the dcache as above for readdir. noquotadf Report overall filesystem usage in statfs instead of using the root directory quota. nocopyfrom Don't use the RADOS 'copy-from' operation to perform remote object copies. Currently, it's only used in copy_file_range, which will revert to the default VFS implementation if this option is used. recover_session= Set auto reconnect mode in the case where the client is blocklisted. The available modes are "no" and "clean". The default is "no". * no: never attempt to reconnect when client detects that it has been blocklisted. Operations will generally fail after being blocklisted. * clean: client reconnects to the ceph cluster automatically when it detects that it has been blocklisted. During reconnect, client drops dirty data/metadata, invalidates page caches and writable file handles. After reconnect, file locks become stale because the MDS loses track of them. If an inode contains any stale file locks, read/write on the inode is not allowed until applications release all stale file locks. h]hdefinition_list)}(hhh](hdefinition_list_item)}(hmon_addr=ip_address[:port][/ip_address[:port]] Monitor address to the cluster. This is used to bootstrap the connection to the cluster. Once connection is established, the monitor addresses in the monitor map are followed. h](hterm)}(h.mon_addr=ip_address[:port][/ip_address[:port]]h]h.mon_addr=ip_address[:port][/ip_address[:port]]}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubh definition)}(hhh]h)}(hMonitor address to the cluster. This is used to bootstrap the connection to the cluster. Once connection is established, the monitor addresses in the monitor map are followed.h]hMonitor address to the cluster. This is used to bootstrap the connection to the cluster. Once connection is established, the monitor addresses in the monitor map are followed.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(h@fsid=cluster-id FSID of the cluster (from `ceph fsid` command). h](j)}(hfsid=cluster-idh]hfsid=cluster-id}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(h/FSID of the cluster (from `ceph fsid` command).h](hFSID of the cluster (from }(hjhhhNhNubjb)}(h `ceph fsid`h]h ceph fsid}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jahjubh command).}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hXip=A.B.C.D[:N] Specify the IP and/or port the client should bind to locally. There is normally not much reason to do this. If the IP is not specified, the client's IP address is determined by looking at the address its connection to the monitor originates from. h](j)}(hip=A.B.C.D[:N]h]hip=A.B.C.D[:N]}(hj,hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhj(ubj)}(hhh]h)}(hSpecify the IP and/or port the client should bind to locally. There is normally not much reason to do this. If the IP is not specified, the client's IP address is determined by looking at the address its connection to the monitor originates from.h]hSpecify the IP and/or port the client should bind to locally. There is normally not much reason to do this. If the IP is not specified, the client’s IP address is determined by looking at the address its connection to the monitor originates from.}(hj=hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj:ubah}(h]h ]h"]h$]h&]uh1jhj(ubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hBwsize=X Specify the maximum write size in bytes. Default: 64 MB. h](j)}(hwsize=Xh]hwsize=X}(hj[hhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjWubj)}(hhh]h)}(h9Specify the maximum write size in bytes. Default: 64 MB.h]h9Specify the maximum write size in bytes. Default: 64 MB.}(hjlhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjiubah}(h]h ]h"]h$]h&]uh1jhjWubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hArsize=X Specify the maximum read size in bytes. Default: 64 MB. h](j)}(hrsize=Xh]hrsize=X}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(h8Specify the maximum read size in bytes. Default: 64 MB.h]h8Specify the maximum read size in bytes. Default: 64 MB.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hFrasize=X Specify the maximum readahead size in bytes. Default: 8 MB. h](j)}(hrasize=Xh]hrasize=X}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(h Set auto reconnect mode in the case where the client is blocklisted. The available modes are "no" and "clean". The default is "no". * no: never attempt to reconnect when client detects that it has been blocklisted. Operations will generally fail after being blocklisted. * clean: client reconnects to the ceph cluster automatically when it detects that it has been blocklisted. During reconnect, client drops dirty data/metadata, invalidates page caches and writable file handles. After reconnect, file locks become stale because the MDS loses track of them. If an inode contains any stale file locks, read/write on the inode is not allowed until applications release all stale file locks. h](j)}(hrecover_session=h]hrecover_session=}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh](h)}(hSet auto reconnect mode in the case where the client is blocklisted. The available modes are "no" and "clean". The default is "no".h]hSet auto reconnect mode in the case where the client is blocklisted. The available modes are “no” and “clean”. The default is “no”.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hhh](h)}(hno: never attempt to reconnect when client detects that it has been blocklisted. Operations will generally fail after being blocklisted. h]h)}(hno: never attempt to reconnect when client detects that it has been blocklisted. Operations will generally fail after being blocklisted.h]hno: never attempt to reconnect when client detects that it has been blocklisted. Operations will generally fail after being blocklisted.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubh)}(hXclean: client reconnects to the ceph cluster automatically when it detects that it has been blocklisted. During reconnect, client drops dirty data/metadata, invalidates page caches and writable file handles. After reconnect, file locks become stale because the MDS loses track of them. If an inode contains any stale file locks, read/write on the inode is not allowed until applications release all stale file locks. h]h)}(hXclean: client reconnects to the ceph cluster automatically when it detects that it has been blocklisted. During reconnect, client drops dirty data/metadata, invalidates page caches and writable file handles. After reconnect, file locks become stale because the MDS loses track of them. If an inode contains any stale file locks, read/write on the inode is not allowed until applications release all stale file locks.h]hXclean: client reconnects to the ceph cluster automatically when it detects that it has been blocklisted. During reconnect, client drops dirty data/metadata, invalidates page caches and writable file handles. After reconnect, file locks become stale because the MDS loses track of them. If an inode contains any stale file locks, read/write on the inode is not allowed until applications release all stale file locks.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubeh}(h]h ]h"]h$]h&]jjuh1hhhhKhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjubeh}(h]h ]h"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h] mount-optionsah ]h"] mount optionsah$]h&]uh1hhhhhhhhK}ubh)}(hhh](h)}(hMore Informationh]hMore Information}(hj9hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhKubj)}(hhh](j)}(hEFor more information on Ceph, see the home page at https://ceph.com/ h](j)}(h2For more information on Ceph, see the home page ath]h2For more information on Ceph, see the home page at}(hjNhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjJubj)}(hhh]h)}(hhttps://ceph.com/h]h reference)}(hjah]hhttps://ceph.com/}(hjehhhNhNubah}(h]h ]h"]h$]h&]refurijauh1jchj_ubah}(h]h ]h"]h$]h&]uh1hhhhKhj\ubah}(h]h ]h"]h$]h&]uh1jhjJubeh}(h]h ]h"]h$]h&]uh1jhhhKhjGubj)}(h^The Linux kernel client source tree is available at - https://github.com/ceph/ceph-client.git h](j)}(h3The Linux kernel client source tree is available ath]h3The Linux kernel client source tree is available at}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(hhh]h)}(h(https://github.com/ceph/ceph-client.git h]h)}(h'https://github.com/ceph/ceph-client.gith]jd)}(hjh]h'https://github.com/ceph/ceph-client.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jchjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]j-uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjGhhubj)}(hIand the source for the full system is at https://github.com/ceph/ceph.gith](j)}(h(and the source for the full system is ath]h(and the source for the full system is at}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhhKhjubj)}(hhh]h)}(h https://github.com/ceph/ceph.gith]jd)}(hjh]h https://github.com/ceph/ceph.git}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jchjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhhhKhjGhhubeh}(h]h ]h"]h$]h&]uh1jhj6hhhhhNubeh}(h]more-informationah ]h"]more informationah$]h&]uh1hhhhhhhhKubeh}(h]ceph-distributed-file-systemah ]h"]ceph distributed file systemah$]h&]uh1hhhhhhhhKubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksentryfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerjDerror_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourceh _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}nameids}(jjjjj3j0jju nametypes}(jjj3juh}(jhjjj0jjj6u footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages]transform_messages] transformerN include_log] decorationNhhub.