Searched refs:NFS (Results 1 – 25 of 147) sorted by relevance
123456
3 tristate "NFS client support"14 To mount file systems exported by NFS servers, you also need to18 mount(8) man page. More detail about the Linux NFS client21 Below you can choose which versions of the NFS protocol are22 available in the kernel to mount NFS servers. Support for NFS25 To configure a system which mounts its root file system via NFS28 system on NFS" below. You cannot compile this file system as a34 tristate "NFS client support for NFS version 2"38 This option enables support for version 2 of the NFS protocol39 (RFC 1094) in the kernel's NFS client.[all …]
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 which22 To export local file systems using NFS, you also need to install25 the Linux NFS server implementation is available via the28 Below you can choose which versions of the NFS protocol are29 available to clients mounting the NFS server on this system.30 Support for NFS version 3 (RFC 1813) is always available when36 bool "NFS server support for NFS version 2 (DEPRECATED)"40 NFSv2 (RFC 1094) was the first publicly-released version of NFS.[all …]
2 Setting up NFS/RDMA14 This document describes how to install and setup the Linux NFS/RDMA client17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server35 use with NFS/RDMA.46 The first kernel release to contain both the NFS/RDMA client and server was55 An NFS/RDMA mount point can be obtained by using the mount.nfs command in57 version with support for NFS/RDMA mounts, but for various reasons we73 these to create an NFS/RDMA enabled mount command), the installation85 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 …]
2 NFS Client5 The NFS client8 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 NFSv313 The Linux NFS client currently supports all the above published versions,18 special features of the NFS client that can be configured by system39 used together with a system's node name when an NFS client identifies itself to44 anything that is believed to be unique across all NFS clients. An53 This string can be stored in an NFS client's grub.conf, or it can be provided57 This uniquifier string will be the same for all NFS clients running in[all …]
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
2 Mounting the root filesystem via NFS (nfsroot)22 Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The23 following text describes on how to use NFS for the root filesystem. For the rest24 of this text 'client' means the diskless system, and 'server' means the NFS33 In order to use nfsroot, NFS client support needs to be selected as54 This is necessary to enable the pseudo-NFS-device. Note that it's not a55 real device but just a synonym to tell the kernel to use NFS instead of63 <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 …]
5 The Linux NFS server now supports the pNFS block layout extension. In this6 case the NFS server acts as Metadata Server (MDS) for pNFS, which in addition7 to handling all the metadata access to the NFS export also hands out layouts11 To use pNFS block layouts with the Linux NFS server the exported file
2 NFS ID Mapper5 Id mapper is used by NFS to translate user and group ids into names, and to8 ways NFS could obtain this information: placing a call to /sbin/request-key11 NFS will attempt to call /sbin/request-key first. If this succeeds, the20 in a custom NFS idmap cache.
2 NFS title
2 Kernel NFS Server Statistics8 which the kernel NFS server makes available to userspace. These31 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, this52 (e.g. an NFS or UDP socket or an NFS/RDMA endpoint).54 Depending on the NFS workload patterns and various network stack57 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 …]
1 Reexporting NFS filesystems7 It is possible to reexport an NFS filesystem over NFS. However, this17 We require the "fsid=" export option on any reexport of an NFS28 The NFS protocol's normal reboot recovery mechanisms don't work for the55 by an NFS server without asking the server vendor.106 NFS since NFSv4 supports ALLOW and DENY bits taken from Windows, which110 against other NFS users, not against processes accessing the exported
6 implement RPCGSS authentication in kernel RPC servers such as the NFS7 server and the NFS client's NFSv4.0 callback server. (But note that24 Authentication for NFS. Although GSSAPI is itself completely mechanism25 agnostic, in many cases only the KRB5 mechanism is supported by NFS46 NFS Server Legacy Upcall Mechanism67 NFS Server New RPC Upcall Mechanism
127 "co_ownerid" string starting with the words "Linux NFS" followed by134 - NFS-root (diskless) clients, where the local DHCP server (or139 to provide a unique host name, then there can be multiple NFS143 common NFS server. If hostnames are not assigned centrally175 If NFS with Kerberos is not configured, a Linux NFSv4 client uses183 When a Kerberos keytab is present on a Linux NFS client, the client192 Additionally, the Linux NFS client uses the RPCSEC_GSS security
5 SUMMARY = "NFS package groups"11 SUMMARY:${PN}-client = "NFS client"14 SUMMARY:${PN}-server = "NFS server"
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."
20 NFS, enumerator33 {TransferProtocolType::NFS, "NFS"},
21 NFS, enumerator55 {TransferProtocolType::NFS, "NFS"},
33 NFS, enumerator77 {TransferProtocolType::NFS, "NFS"},
93 NFS,190 {TransferProtocolType::NFS, "NFS"},92 NFS, global() enumerator
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 support76 The NFS export feature creates an index on copy up of every file and83 Note, that the NFS export feature is not backward compatible.
6 Coda is an advanced network file system, similar to NFS in that it9 disk. Coda has several advantages over NFS: support for
14 non-block filesystems which provide their own BDI, such as NFS69 most of the write-back cache. For example in case of an NFS83 in case of an NFS mount that is prone to get stuck, or a FUSE mount110 most of the write-back cache. For example in case of an NFS
57 netmask, ethaddr, eth1addr, rootpath (if using NFS root),61 want an NFS root or a ramdisk root:
1 define KFEATURE_DESCRIPTION "Enable NFS"