| /openbmc/linux/fs/nfs/ |
| H A D | Kconfig | 3 tristate "NFS client support"
14 To mount file systems exported by NFS servers, you also need to
18 mount(8) man page. More detail about the Linux NFS client
21 Below you can choose which versions of the NFS protocol are
22 available in the kernel to mount NFS servers. Support for NFS
25 To configure a system which mounts its root file system via NFS
28 system on NFS" below. You cannot compile this file system as a
34 tristate "NFS client support for NFS version 2"
38 This option enables support for version 2 of the NFS protocol
39 (RFC 1094) in the kernel's NFS client.
[all …]
|
| /openbmc/linux/fs/nfsd/ |
| H A D | Kconfig | 3 tristate "NFS server support"
16 protocol. To compile the NFS server support as a module,
19 You may choose to use a user-space NFS server instead, in which
22 To export local file systems using NFS, you also need to install
25 the Linux NFS server implementation is available via the
28 Below you can choose which versions of the NFS protocol are
29 available to clients mounting the NFS server on this system.
30 Support for NFS version 3 (RFC 1813) is always available when
36 bool "NFS server support for NFS version 2 (DEPRECATED)"
40 NFSv2 (RFC 1094) was the first publicly-released version of NFS.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/nfs/ |
| H A D | nfs-rdma.rst | 2 Setting up NFS/RDMA
14 This document describes how to install and setup the Linux NFS/RDMA client
17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
35 use with NFS/RDMA.
46 The first kernel release to contain both the NFS/RDMA client and server was
55 An NFS/RDMA mount point can be obtained by using the mount.nfs command in
57 version with support for NFS/RDMA mounts, but for various reasons we
73 these to create an NFS/RDMA enabled mount command), the installation
85 the utils/mount directory. This binary can be used to initiate NFS v2, v3,
96 In this location, mount.nfs will be invoked automatically for NFS mounts
[all …]
|
| H A D | nfs-client.rst | 2 NFS Client
5 The NFS client
8 The NFS version 2 protocol was first documented in RFC1094 (March 1989).
9 Since then two more major releases of NFS have been published, with NFSv3
13 The Linux NFS client currently supports all the above published versions,
18 special features of the NFS client that can be configured by system
39 used together with a system's node name when an NFS client identifies itself to
44 anything that is believed to be unique across all NFS clients. An
53 This string can be stored in an NFS client's grub.conf, or it can be provided
57 This uniquifier string will be the same for all NFS clients running in
[all …]
|
| H A D | pnfs-scsi-server.rst | 6 This document describes support for pNFS SCSI layouts in the Linux NFS server.
7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS,
8 which in addition to handling all the metadata access to the NFS export,
12 To use pNFS SCSI layouts with the Linux NFS server, the exported file
|
| H A D | nfsroot.rst | 2 Mounting the root filesystem via NFS (nfsroot)
22 Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The
23 following text describes on how to use NFS for the root filesystem. For the rest
24 of this text 'client' means the diskless system, and 'server' means the NFS
33 In order to use nfsroot, NFS client support needs to be selected as
54 This is necessary to enable the pseudo-NFS-device. Note that it's not a
55 real device but just a synonym to tell the kernel to use NFS instead of
63 <server-ip> Specifies the IP address of the NFS server.
66 servers for IP autoconfiguration and NFS.
73 <nfs-options> Standard NFS options. All options are separated by commas.
[all …]
|
| H A D | pnfs-block-server.rst | 5 The Linux NFS server now supports the pNFS block layout extension. In this
6 case the NFS server acts as Metadata Server (MDS) for pNFS, which in addition
7 to handling all the metadata access to the NFS export also hands out layouts
11 To use pNFS block layouts with the Linux NFS server the exported file
|
| H A D | nfs-idmapper.rst | 2 NFS ID Mapper
5 Id mapper is used by NFS to translate user and group ids into names, and to
8 ways NFS could obtain this information: placing a call to /sbin/request-key
11 NFS will attempt to call /sbin/request-key first. If this succeeds, the
20 in a custom NFS idmap cache.
|
| H A D | index.rst | 2 NFS title
|
| /openbmc/linux/Documentation/filesystems/nfs/ |
| H A D | knfsd-stats.rst | 2 Kernel NFS Server Statistics
8 which the kernel NFS server makes available to userspace. These
31 for each NFS thread pool.
38 The id number of the NFS thread pool to which this line applies.
49 Counts how many NFS packets have arrived. More precisely, this
52 (e.g. an NFS or UDP socket or an NFS/RDMA endpoint).
54 Depending on the NFS workload patterns and various network stack
57 of NFS calls received (which statistic is available elsewhere).
60 due to NFS network traffic.
63 Counts how many times an NFS transport is enqueued to wait for
[all …]
|
| H A D | reexport.rst | 1 Reexporting NFS filesystems
7 It is possible to reexport an NFS filesystem over NFS. However, this
17 We require the "fsid=" export option on any reexport of an NFS
28 The NFS protocol's normal reboot recovery mechanisms don't work for the
55 by an NFS server without asking the server vendor.
106 NFS since NFSv4 supports ALLOW and DENY bits taken from Windows, which
110 against other NFS users, not against processes accessing the exported
|
| H A D | rpc-server-gss.rst | 6 implement RPCGSS authentication in kernel RPC servers such as the NFS
7 server and the NFS client's NFSv4.0 callback server. (But note that
24 Authentication for NFS. Although GSSAPI is itself completely mechanism
25 agnostic, in many cases only the KRB5 mechanism is supported by NFS
46 NFS Server Legacy Upcall Mechanism
67 NFS Server New RPC Upcall Mechanism
|
| H A D | client-identifier.rst | 127 "co_ownerid" string starting with the words "Linux NFS" followed by
134 - NFS-root (diskless) clients, where the local DHCP server (or
139 to provide a unique host name, then there can be multiple NFS
143 common NFS server. If hostnames are not assigned centrally
175 If NFS with Kerberos is not configured, a Linux NFSv4 client uses
183 When a Kerberos keytab is present on a Linux NFS client, the client
192 Additionally, the Linux NFS client uses the RPCSEC_GSS security
|
| H A D | index.rst | 2 NFS title
|
| /openbmc/openbmc/poky/meta/recipes-core/packagegroups/ |
| H A D | packagegroup-core-nfs.bb | 5 SUMMARY = "NFS package groups"
11 SUMMARY:${PN}-client = "NFS client"
14 SUMMARY:${PN}-server = "NFS server"
|
| /openbmc/openbmc/poky/meta/recipes-devtools/unfs3/ |
| H A D | unfs3_git.bb | 1 SUMMARY = "Userspace NFS server v3 protocol"
3 specification. It provides a daemon for the MOUNT and NFS protocols, which \
4 are used by NFS clients for accessing files on the server."
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | license_service.hpp | 20 NFS, enumerator
33 {TransferProtocolType::NFS, "NFS"},
|
| H A D | update_service.hpp | 21 NFS, enumerator
55 {TransferProtocolType::NFS, "NFS"},
|
| H A D | virtual_media.hpp | 33 NFS, enumerator
77 {TransferProtocolType::NFS, "NFS"},
|
| H A D | log_service.hpp | 92 NFS, enumerator
188 {TransferProtocolType::NFS, "NFS"},
|
| /openbmc/linux/fs/overlayfs/ |
| H A D | Kconfig | 65 bool "Overlayfs: turn on NFS export feature by default"
71 the index directory to decode overlay NFS file handles by default.
72 In this case, it is still possible to turn off NFS export support
76 The NFS export feature creates an index on copy up of every file and
83 Note, that the NFS export feature is not backward compatible.
|
| /openbmc/linux/fs/coda/ |
| H A D | Kconfig | 6 Coda is an advanced network file system, similar to NFS in that it
9 disk. Coda has several advantages over NFS: support for
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-bdi | 14 non-block filesystems which provide their own BDI, such as NFS
69 most of the write-back cache. For example in case of an NFS
83 in case of an NFS mount that is prone to get stuck, or a FUSE mount
110 most of the write-back cache. For example in case of an NFS
|
| /openbmc/u-boot/board/freescale/mpc8323erdb/ |
| H A D | README | 57 netmask, ethaddr, eth1addr, rootpath (if using NFS root),
61 want an NFS root or a ramdisk root:
|
| /openbmc/openbmc/meta-phosphor/recipes-kernel/linux/nfs/ |
| H A D | nfs.scc | 1 define KFEATURE_DESCRIPTION "Enable NFS"
|