€•cQ      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ./translations/zh_CN/admin-guide/nfs/nfs-client”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ./translations/zh_TW/admin-guide/nfs/nfs-client”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ./translations/it_IT/admin-guide/nfs/nfs-client”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ./translations/ja_JP/admin-guide/nfs/nfs-client”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ./translations/ko_KR/admin-guide/nfs/nfs-client”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ./translations/sp_SP/admin-guide/nfs/nfs-client”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ
NFS Client”h]”hŒ
NFS Client”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒH/var/lib/git/docbuild/linux/Documentation/admin-guide/nfs/nfs-client.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒThe NFS client”h]”hŒThe NFS client”…””}”(hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h KubhŒ	paragraph”“”)”}”(hŒÞThe NFS version 2 protocol was first documented in RFC1094 (March 1989).
Since then two more major releases of NFS have been published, with NFSv3
being documented in RFC1813 (June 1995), and NFSv4 in RFC3530 (April
2003).”h]”hŒÞThe NFS version 2 protocol was first documented in RFC1094 (March 1989).
Since then two more major releases of NFS have been published, with NFSv3
being documented in RFC1813 (June 1995), and NFSv4 in RFC3530 (April
2003).”…””}”(hhÊhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒžThe Linux NFS client currently supports all the above published versions,
and work is in progress on adding support for minor version 1 of the NFSv4
protocol.”h]”hŒžThe Linux NFS client currently supports all the above published versions,
and work is in progress on adding support for minor version 1 of the NFSv4
protocol.”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒ™The purpose of this document is to provide information on some of the
special features of the NFS client that can be configured by system
administrators.”h]”hŒ™The purpose of this document is to provide information on some of the
special features of the NFS client that can be configured by system
administrators.”…””}”(hhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubeh}”(h]”Œthe-nfs-client”ah ]”h"]”Œthe nfs client”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒThe nfs4_unique_id parameter”h]”hŒThe nfs4_unique_id parameter”…””}”(hhÿhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhühžhhŸh¶h KubhÉ)”}”(hX8  NFSv4 requires clients to identify themselves to servers with a unique
string.  File open and lock state shared between one client and one server
is associated with this identity.  To support robust NFSv4 state recovery
and transparent state migration, this identity string must not change
across client reboots.”h]”hX8  NFSv4 requires clients to identify themselves to servers with a unique
string.  File open and lock state shared between one client and one server
is associated with this identity.  To support robust NFSv4 state recovery
and transparent state migration, this identity string must not change
across client reboots.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KhhühžhubhÉ)”}”(hX  Without any other intervention, the Linux client uses a string that contains
the local system's node name.  System administrators, however, often do not
take care to ensure that node names are fully qualified and do not change
over the lifetime of a client system.  Node names can have other
administrative requirements that require particular behavior that does not
work well as part of an nfs_client_id4 string.”h]”hXŸ  Without any other intervention, the Linux client uses a string that contains
the local systemâ€™s node name.  System administrators, however, often do not
take care to ensure that node names are fully qualified and do not change
over the lifetime of a client system.  Node names can have other
administrative requirements that require particular behavior that does not
work well as part of an nfs_client_id4 string.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KhhühžhubhÉ)”}”(hX  The nfs.nfs4_unique_id boot parameter specifies a unique string that can be
used together with  a system's node name when an NFS client identifies itself to
a server.  Thus, if the system's node name is not unique, its
nfs.nfs4_unique_id can help prevent collisions with other clients.”h]”hX!  The nfs.nfs4_unique_id boot parameter specifies a unique string that can be
used together with  a systemâ€™s node name when an NFS client identifies itself to
a server.  Thus, if the systemâ€™s node name is not unique, its
nfs.nfs4_unique_id can help prevent collisions with other clients.”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K&hhühžhubhÉ)”}”(hX)  The nfs.nfs4_unique_id string is typically a UUID, though it can contain
anything that is believed to be unique across all NFS clients.  An
nfs4_unique_id string should be chosen when a client system is installed,
just as a system's root file system gets a fresh UUID in its label at
install time.”h]”hX+  The nfs.nfs4_unique_id string is typically a UUID, though it can contain
anything that is believed to be unique across all NFS clients.  An
nfs4_unique_id string should be chosen when a client system is installed,
just as a systemâ€™s root file system gets a fresh UUID in its label at
install time.”…””}”(hj7  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K+hhühžhubhÉ)”}”(hŒÙThe string should remain fixed for the lifetime of the client.  It can be
changed safely if care is taken that the client shuts down cleanly and all
outstanding NFSv4 state has expired, to prevent loss of NFSv4 state.”h]”hŒÙThe string should remain fixed for the lifetime of the client.  It can be
changed safely if care is taken that the client shuts down cleanly and all
outstanding NFSv4 state has expired, to prevent loss of NFSv4 state.”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K1hhühžhubhÉ)”}”(hŒ«This string can be stored in an NFS client's grub.conf, or it can be provided
via a net boot facility such as PXE.  It may also be specified as an nfs.ko
module parameter.”h]”hŒ­This string can be stored in an NFS clientâ€™s grub.conf, or it can be provided
via a net boot facility such as PXE.  It may also be specified as an nfs.ko
module parameter.”…””}”(hjS  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K5hhühžhubhÉ)”}”(hŒïThis uniquifier string will be the same for all NFS clients running in
containers unless it is overridden by a value written to
/sys/fs/nfs/net/nfs_client/identifier which will be local to the network
namespace of the process which writes.”h]”hŒïThis uniquifier string will be the same for all NFS clients running in
containers unless it is overridden by a value written to
/sys/fs/nfs/net/nfs_client/identifier which will be local to the network
namespace of the process which writes.”…””}”(hja  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K9hhühžhubeh}”(h]”Œthe-nfs4-unique-id-parameter”ah ]”h"]”Œthe nfs4_unique_id parameter”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒThe DNS resolver”h]”hŒThe DNS resolver”…””}”(hjz  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjw  hžhhŸh¶h K@ubhÉ)”}”(hX  NFSv4 allows for one server to refer the NFS client to data that has been
migrated onto another server by means of the special "fs_locations"
attribute. See `RFC3530 Section 6: Filesystem Migration and Replication`_ and
`Implementation Guide for Referrals in NFSv4`_.”h]”(hŒ¡NFSv4 allows for one server to refer the NFS client to data that has been
migrated onto another server by means of the special â€œfs_locationsâ€
attribute. See ”…””}”(hjˆ  hžhhŸNh NubhŒ	reference”“”)”}”(hŒ:`RFC3530 Section 6: Filesystem Migration and Replication`_”h]”hŒ7RFC3530 Section 6: Filesystem Migration and Replication”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ7RFC3530 Section 6: Filesystem Migration and Replication”Œrefuri”Œ-https://tools.ietf.org/html/rfc3530#section-6”uh1j  hjˆ  Œresolved”KubhŒ and
”…””}”(hjˆ  hžhhŸNh Nubj‘  )”}”(hŒ.`Implementation Guide for Referrals in NFSv4`_”h]”hŒ+Implementation Guide for Referrals in NFSv4”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ+Implementation Guide for Referrals in NFSv4”j¢  Œ9https://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00”uh1j  hjˆ  j¤  KubhŒ.”…””}”(hjˆ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KBhjw  hžhubhŒtarget”“”)”}”(hŒk.. _RFC3530 Section 6\: Filesystem Migration and Replication: https://tools.ietf.org/html/rfc3530#section-6”h]”h}”(h]”Œ6rfc3530-section-6-filesystem-migration-and-replication”ah ]”h"]”Œ7rfc3530 section 6: filesystem migration and replication”ah$]”h&]”j¢  j£  uh1jÄ  h KGhjw  hžhhŸh¶Œ
referenced”KubjÅ  )”}”(hŒj.. _Implementation Guide for Referrals in NFSv4: https://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00”h]”h}”(h]”Œ+implementation-guide-for-referrals-in-nfsv4”ah ]”h"]”Œ+implementation guide for referrals in nfsv4”ah$]”h&]”j¢  j¹  uh1jÄ  h KHhjw  hžhhŸh¶jÒ  KubhÉ)”}”(hX  The fs_locations information can take the form of either an ip address and
a path, or a DNS hostname and a path. The latter requires the NFS client to
do a DNS lookup in order to mount the new volume, and hence the need for an
upcall to allow userland to provide this service.”h]”hX  The fs_locations information can take the form of either an ip address and
a path, or a DNS hostname and a path. The latter requires the NFS client to
do a DNS lookup in order to mount the new volume, and hence the need for an
upcall to allow userland to provide this service.”…””}”(hjß  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KJhjw  hžhubhÉ)”}”(hŒAssuming that the user has the 'rpc_pipefs' filesystem mounted in the usual
/var/lib/nfs/rpc_pipefs, the upcall consists of the following steps:”h]”hŒ”Assuming that the user has the â€˜rpc_pipefsâ€™ filesystem mounted in the usual
/var/lib/nfs/rpc_pipefs, the upcall consists of the following steps:”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KOhjw  hžhubhŒblock_quote”“”)”}”(hXw  (1) The process checks the dns_resolve cache to see if it contains a
    valid entry. If so, it returns that entry and exits.

(2) If no valid entry exists, the helper script '/sbin/nfs_cache_getent'
    (may be changed using the 'nfs.cache_getent' kernel boot parameter)
    is run, with two arguments:
    - the cache name, "dns_resolve"
    - the hostname to resolve

(3) After looking up the corresponding ip address, the helper script
    writes the result into the rpc_pipefs pseudo-file
    '/var/lib/nfs/rpc_pipefs/cache/dns_resolve/channel'
    in the following (text) format:

             "<ip address> <hostname> <ttl>\n"

    Where <ip address> is in the usual IPv4 (123.456.78.90) or IPv6
    (ffee:ddcc:bbaa:9988:7766:5544:3322:1100, ffee::1100, ...) format.
    <hostname> is identical to the second argument of the helper
    script, and <ttl> is the 'time to live' of this cache entry (in
    units of seconds).

    .. note::
         If <ip address> is invalid, say the string "0", then a negative
         entry is created, which will cause the kernel to treat the hostname
         as having no valid DNS translation.


”h]”hŒenumerated_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒvThe process checks the dns_resolve cache to see if it contains a
valid entry. If so, it returns that entry and exits.
”h]”hÉ)”}”(hŒuThe process checks the dns_resolve cache to see if it contains a
valid entry. If so, it returns that entry and exits.”h]”hŒuThe process checks the dns_resolve cache to see if it contains a
valid entry. If so, it returns that entry and exits.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KRhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj  )”}”(hŒßIf no valid entry exists, the helper script '/sbin/nfs_cache_getent'
(may be changed using the 'nfs.cache_getent' kernel boot parameter)
is run, with two arguments:
- the cache name, "dns_resolve"
- the hostname to resolve
”h]”hÉ)”}”(hŒÞIf no valid entry exists, the helper script '/sbin/nfs_cache_getent'
(may be changed using the 'nfs.cache_getent' kernel boot parameter)
is run, with two arguments:
- the cache name, "dns_resolve"
- the hostname to resolve”h]”hŒêIf no valid entry exists, the helper script â€˜/sbin/nfs_cache_getentâ€™
(may be changed using the â€˜nfs.cache_getentâ€™ kernel boot parameter)
is run, with two arguments:
- the cache name, â€œdns_resolveâ€
- the hostname to resolve”…””}”(hj$  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KUhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj  )”}”(hXÌ  After looking up the corresponding ip address, the helper script
writes the result into the rpc_pipefs pseudo-file
'/var/lib/nfs/rpc_pipefs/cache/dns_resolve/channel'
in the following (text) format:

         "<ip address> <hostname> <ttl>\n"

Where <ip address> is in the usual IPv4 (123.456.78.90) or IPv6
(ffee:ddcc:bbaa:9988:7766:5544:3322:1100, ffee::1100, ...) format.
<hostname> is identical to the second argument of the helper
script, and <ttl> is the 'time to live' of this cache entry (in
units of seconds).

.. note::
     If <ip address> is invalid, say the string "0", then a negative
     entry is created, which will cause the kernel to treat the hostname
     as having no valid DNS translation.


”h]”(hÉ)”}”(hŒÆAfter looking up the corresponding ip address, the helper script
writes the result into the rpc_pipefs pseudo-file
'/var/lib/nfs/rpc_pipefs/cache/dns_resolve/channel'
in the following (text) format:”h]”hŒÊAfter looking up the corresponding ip address, the helper script
writes the result into the rpc_pipefs pseudo-file
â€˜/var/lib/nfs/rpc_pipefs/cache/dns_resolve/channelâ€™
in the following (text) format:”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K[hj8  ubjü  )”}”(hŒ""<ip address> <hostname> <ttl>\n"
”h]”hÉ)”}”(hŒ!"<ip address> <hostname> <ttl>\n"”h]”hŒ%â€œ<ip address> <hostname> <ttl> nâ€”…””}”(hjN  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K`hjJ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh¶h K`hj8  ubhÉ)”}”(hX  Where <ip address> is in the usual IPv4 (123.456.78.90) or IPv6
(ffee:ddcc:bbaa:9988:7766:5544:3322:1100, ffee::1100, ...) format.
<hostname> is identical to the second argument of the helper
script, and <ttl> is the 'time to live' of this cache entry (in
units of seconds).”h]”hX  Where <ip address> is in the usual IPv4 (123.456.78.90) or IPv6
(ffee:ddcc:bbaa:9988:7766:5544:3322:1100, ffee::1100, ...) format.
<hostname> is identical to the second argument of the helper
script, and <ttl> is the â€˜time to liveâ€™ of this cache entry (in
units of seconds).”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kbhj8  ubhŒnote”“”)”}”(hŒ§If <ip address> is invalid, say the string "0", then a negative
entry is created, which will cause the kernel to treat the hostname
as having no valid DNS translation.”h]”hÉ)”}”(hŒ§If <ip address> is invalid, say the string "0", then a negative
entry is created, which will cause the kernel to treat the hostname
as having no valid DNS translation.”h]”hŒ«If <ip address> is invalid, say the string â€œ0â€, then a negative
entry is created, which will cause the kernel to treat the hostname
as having no valid DNS translation.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kihjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jp  hj8  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”Œ(”Œsuffix”Œ)”uh1j  hjý  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jû  hŸh¶h KRhjw  hžhubeh}”(h]”Œthe-dns-resolver”ah ]”h"]”Œthe dns resolver”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K@ubh¢)”}”(hhh]”(h§)”}”(hŒ%A basic sample /sbin/nfs_cache_getent”h]”hŒ%A basic sample /sbin/nfs_cache_getent”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjª  hžhhŸh¶h KqubhŒliteral_block”“”)”}”(hXû  #!/bin/bash
#
ttl=600
#
cut=/usr/bin/cut
getent=/usr/bin/getent
rpc_pipefs=/var/lib/nfs/rpc_pipefs
#
die()
{
    echo "Usage: $0 cache_name entry_name"
    exit 1
}

[ $# -lt 2 ] && die
cachename="$1"
cache_path=${rpc_pipefs}/cache/${cachename}/channel

case "${cachename}" in
    dns_resolve)
        name="$2"
        result="$(${getent} hosts ${name} | ${cut} -f1 -d\ )"
        [ -z "${result}" ] && result="0"
        ;;
    *)
        die
        ;;
esac
echo "${result} ${name} ${ttl}" >${cache_path}”h]”hXû  #!/bin/bash
#
ttl=600
#
cut=/usr/bin/cut
getent=/usr/bin/getent
rpc_pipefs=/var/lib/nfs/rpc_pipefs
#
die()
{
    echo "Usage: $0 cache_name entry_name"
    exit 1
}

[ $# -lt 2 ] && die
cachename="$1"
cache_path=${rpc_pipefs}/cache/${cachename}/channel

case "${cachename}" in
    dns_resolve)
        name="$2"
        result="$(${getent} hosts ${name} | ${cut} -f1 -d\ )"
        [ -z "${result}" ] && result="0"
        ;;
    *)
        die
        ;;
esac
echo "${result} ${name} ${ttl}" >${cache_path}”…””}”hj½  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”Œforce”‰Œlanguage”Œsh”Œhighlight_args”}”uh1j»  hŸh¶h Krhjª  hžhubeh}”(h]”Œ$a-basic-sample-sbin-nfs-cache-getent”ah ]”h"]”Œ%a basic sample /sbin/nfs_cache_getent”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kqubeh}”(h]”Œ
nfs-client”ah ]”h"]”Œ
nfs client”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”(Œ7rfc3530 section 6: filesystem migration and replication”]”j’  aŒ+implementation guide for referrals in nfsv4”]”j©  auŒrefids”}”Œnameids”}”(jß  jÜ  hùhöjt  jq  j§  j¤  jÏ  jÌ  jÜ  jÙ  j×  jÔ  uŒ	nametypes”}”(jß  ‰hù‰jt  ‰j§  ‰jÏ  ˆjÜ  ˆj×  ‰uh}”(jÜ  h£höh·jq  hüj¤  jw  jÌ  jÆ  jÙ  jÓ  jÔ  jª  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.