Search results
From Linux NFS
Create the page "NFSv4" on this wiki!
- PNFS Development Road Map Section 1 describes the status of NFSv4.1 specification, based on the IETF meeting that just ended. ...n1-17.txt] appears to be complete. [http://www1.ietf.org/mail-archive/web/nfsv4/current/msg05155.html pNFS discussions] centered on device ID mappings, lay9 KB (1,390 words) - 21:48, 16 January 2008
- Cluster client migration prototype ...o provide an interface by which an administrator could selectively migrate NFSv4 clients from one server to another (e.g., to take a server down for mainten ...reboot-recovery process. To briefly explain reboot-recovery, when a Linux NFSv4 server starts, it enters a ~90sec phase called a grace period; during this7 KB (1,111 words) - 17:23, 11 January 2008
- PNFS Todo List == NFSv4.1 (sessions) Todo List == ... wants this done from a user's perspective - what would a fully functional NFSv4.1 sessions client see from the server?7 KB (1,098 words) - 16:19, 25 July 2009
- PNFS Setup Instructions <b>Step 1: Setup NFSv4 servers</b>2 KB (341 words) - 15:56, 12 June 2015
- PNFS todo List 2007 * Clean up sessions code to have a clean split between NFSv4.0 and NFSv4.1 ====June 11-15, 2007 Austin - NFSv4.1 todo list====3 KB (418 words) - 05:29, 3 September 2008
- Ipv6PlanningDocument ...2, 3 and 4) and any supported auxiliary protocols (MNT, NLM, NSM, NFS_ACL, NFSv4 callback, rpcbind). User space support (idmapd, gssd, svcgssd, statd, sm-n * support for IPv6 in the client's NFSv4 callback service7 KB (1,130 words) - 14:20, 21 August 2012
- PNFS File-based Distribution Options Distribute NFSv4 state via File System or NFSD The discussion of whether to distribute nfsv4 stateids via the NFSD2 KB (356 words) - 21:29, 10 March 2009
- NFSv41 Introduction Follow instructions for exporting nfsv4.840 B (120 words) - 21:48, 26 July 2013
- Server 4.0 and 4.1 issues Before 3.11, the server's implementation of NFSv4.1 deviates from the spec ([http://tools.ietf.org/search/rfc5661 rfc 5661]) * someone upgrading from NFSv4.0 should experience no loss in functionality;15 KB (2,421 words) - 15:11, 5 August 2014
- Configuring pNFS/spnfsd pNFS is a new NFS feature provided in NFSv4.1, also known as Parallel NFS. Parallel NFS (pNFS) extends Network File Sharing version 4 (NFSv4) to allow clients to directly access file data on the storage used by the8 KB (1,209 words) - 09:46, 18 November 2012
- Fedora pNFS Client Setup wget -O /etc/rc.d/init.d/blkmapd http://www.citi.umich.edu/projects/nfsv4/pnfs/block/download/rh-init.txt nfsv4: bm0=0xfcff8fff,bm1=0x40f9bfff,acl=0x3,sessions,pnfs=LAYOUT_BLOCK_VOLUME8 KB (1,274 words) - 12:14, 15 May 2012
- Nfsd4 server recovery take full advantage of NFSv4.1. An overhaul has been a long-standing todo. * An NFSv4.0 client becomes active as soon as it succesfully performs its first OPEN_C11 KB (1,945 words) - 20:14, 3 August 2011
- Getcwd() incorrectly returning ENOENT NFSv4: Simplify some cache consistency post-op GETATTRs NFSv4: Fix a cache validation bug which causes getcwd() to return ENOENT3 KB (479 words) - 17:35, 22 October 2010
- Read denied because it uses the OPEN state instead of the LOCK state NFSv4: Ensure that we track the NFSv4 lock state in read/write requests. NFSv4: Ensure that we track the NFSv4 lock state in read/write requests.5 KB (814 words) - 19:41, 22 October 2010
- Nfs4 NULL pointer dereference in nfs4 do setlk NFSv4: Fix the 'nolock' option regression NFSv4 should just ignore the 'nolock' option. It is an NFSv2/v3 thing...4 KB (536 words) - 15:26, 25 October 2010
- Server export issues ...andles this; if nothing else, it should error out and give up on automatic nfsv4 support. But document this and make sure it's OK with people. Failures of * Currently NFSv4 won't notice when we cross an export boundary unless it's also a mountpoint3 KB (539 words) - 19:47, 15 December 2020
- Readdir performance results * [[Readdir NFSv4 No Readdir Plus]] * [[Readdir NFSv4 With Readdir Plus]]2 KB (250 words) - 18:59, 7 April 2011
- Readdir NFSv4 With Readdir Plus Note: NFSv4 Readdir plus does not exist in 2.6.36. Numbers for columns 36 and 36NORC a14 KB (1,235 words) - 19:44, 4 April 2011
- FedFsInstallationGuide0.10 ...mmunicates with fileservers using a standard file-access protocol (such as NFSv4). If an NFSv4 client is to use Globally Useful Names (pathnames that appear the same on a6 KB (894 words) - 18:14, 3 February 2014
- Fake DNS Realm ...document describes the basic setup of a fake DNS domain for use in testing NFSv4 (with IPA, Kerberos, Cross-Realm Auth, etc) on [http://fedoraproject.org/ f6 KB (769 words) - 02:37, 1 March 2012
- Old stuff ...ctory delegations, but implementation efforts are currently stalled; see [[NFSv4.1 Directory Delegations]] for experience from an early CITI prototyping eff Core NFSv4.1 support should be up to spec at this point; see [[Server 4.0 and 4.1 issu1 KB (152 words) - 17:54, 4 January 2021
- Introduction to Linux NFS hacking = understanding NFSv4 = ...lated documents from the [https://datatracker.ietf.org/wg/nfsv4/documents/ NFSv4 IETF working group]. Don't read them from start to finish! They're too long8 KB (1,420 words) - 19:44, 15 December 2020
- Soft lockup in nfs commit inode() ...433f83670e7b42cbe75319c208762] NFSv4: Clean up the process of renewing the NFSv4 lease # bad: [77041ed9b49a9e10f374bfa6e482d30ee7a3d46e] NFSv4: Ensure the lockowners are labelled using the fl_owner and/or fl_pid5 KB (870 words) - 17:40, 29 July 2011
- NFStest Valid for NFSv4.0 and NFSv4.1 including pNFS verify proper functionality of pNFS and NFSv4.1 as well:15 KB (2,411 words) - 18:14, 22 March 2023
- FedFsUtilsProject * Tools to manage NFSv4 referrals on Linux NFS servers3 KB (435 words) - 15:46, 27 July 2021
- FedFsInstallationGuide0.9 ...mmunicates with fileservers using a standard file-access protocol (such as NFSv4). If an NFSv4 client is to use Globally Useful Names (pathnames that appear the same on a6 KB (938 words) - 21:07, 3 March 2014
- FedFsNfsRefGuide0.9 ...or the location of that fileset. The server provides that location to the NFSv4 client, which automatically mounts sales.example.net:/ and allows the user8 KB (1,199 words) - 18:58, 9 January 2013
- FedFsNfsReferrals When client NFSv4 support is enabled, NFSv4 referral support is enabled by default in all recent Linux kernel versions. ...that to an IP address before it can contact the referred-to server. Early NFSv4 referral support had no ability to resolve a hostname contained in a locati5 KB (776 words) - 15:44, 9 September 2015
- FedFsNfsServer0.9 ...s them to information that the kernel NFS server can put on the wire as an NFSv4 referral.2 KB (328 words) - 18:06, 9 January 2013
- FedFsGlossary A network filesystem access protocol such as NFSv4 or CIFS.4 KB (670 words) - 17:30, 27 November 2012
- FedFsInstallationGuide0.8 ...mmunicates with fileservers using a standard file-access protocol (such as NFSv4). If an NFSv4 client is to use Globally Useful Names (pathnames that appear the same on a6 KB (912 words) - 16:24, 27 November 2012
- FedFsNfsServer0.8 ...st. The NFS server must convert a junction's location information into an NFSv4 referral which can be sent to NFS clients. ...rts it to information that the kernel NFS server can put on the wire as an NFSv4 referral.2 KB (343 words) - 16:30, 27 November 2012
- FedFsNfsRefGuide0.8 ...or the location of that fileset. The server provides that location to the NFSv4 client, which automatically mounts sales.example.net:/ and allows the user8 KB (1,185 words) - 16:52, 27 November 2012
- P2P Design Specification * draft-myklebust-nfsv4-pnfs-backend-protocol-01.txt * NFSv4 Proxy Open10 KB (1,670 words) - 19:23, 18 January 2013
- Peer-to-peer NFS The nfsv4.1 spec forbids returning ETOOSMALL in this case. [pnfsd: Fix server GETDEVICELIST to comply with NFSv4.1 Draft 13]31 KB (4,458 words) - 18:30, 3 December 2012
- PNFS Development pNFS is part of the first NFSv4 minor version. This space is used to track and share Linux pNFS implementat ...://bugzilla.linux-nfs.org linux-nfs.org Bugzilla] - Read/ Write access by "NFSv4.1 related bugs" group members2 KB (226 words) - 15:13, 23 April 2015
- FedFsNfsServer0.10 ...s them to information that the kernel NFS server can put on the wire as an NFSv4 referral.2 KB (328 words) - 18:02, 3 February 2014
- FedFsNfsRefGuide0.10 ...or the location of that fileset. The server provides that location to the NFSv4 client, which automatically mounts sales.example.net:/ and allows the user8 KB (1,197 words) - 18:09, 3 February 2014
- Dual-protocol support SMB and NFSv4.* support Windows-like ACLs, but use complicated (and different) translatio [http://tools.ietf.org/html/rfc7530#section-9.9 NFSv4 protocol reference]5 KB (750 words) - 14:06, 16 June 2015
- High availability SCSI layout ...trigger recovery behavior on the client which will cause it to reclaim any NFSv4 state and reacquire layouts as necessary.521 B (84 words) - 18:49, 18 December 2015
- Alternate Data Streams The NFSv4 protocol includes "named attributes" ([http://tools.ietf.org/html/rfc7530#s ...would a file, and they can be much larger. The lookup interface differs. NFSv4 provides an [http://tools.ietf.org/html/rfc7530#section-16.17 OPENATTR oper4 KB (604 words) - 19:04, 14 December 2020
- Cluster coherent lock recovery NFSv4 servers are permitted to forget which clients hold which locks on reboot, a2 KB (299 words) - 20:14, 12 December 2016
- NFS for AFS users If we use NFSv4 proxies instead, proxies will hold opens or delegations on the files on the ...arse-grained than NFSv4 ACLs, so information can be lost when a user on an NFSv4 client sets an ACL. This makes ACLs confusing and less useful.13 KB (2,220 words) - 20:35, 27 January 2022
- AFS to NFSv4 ACL conversion If filesystems are migrated from AFS to NFSv4, one of the challenges will be mapping file permissions. ... necessarily imperfect but I think it gets pretty close. If the resulting NFSv4 ACL is stored on a Linux server, the result will be further translated to a6 KB (954 words) - 19:05, 4 August 2021
- NFS re-export ... are limited (to 32 bytes for NFSv2, 64 bytes for NFSv3, and 128 bytes for NFSv4). When we re-export, we take the filehandle returned from the original ser == errors on re-exports of NFSv4.0 filesystems to NFSv2/3 clients ==9 KB (1,461 words) - 22:43, 19 January 2022
- Server-side silly rename NFSv4 actually does have open and close calls, and our server won't free a file u ...rectory for the purpose, and avoid the rmdir). We even added a bit to the NFSv4.1 protocol so that the server can tell the client it does this, allowing th6 KB (1,143 words) - 20:27, 18 January 2022
- NFSv4 quota support NFSv3 had the RQUOTA protocol. NFSv4 has three read-only attributes (see https://tools.ietf.org/html/rfc5661#sec ...all traversal), so ideally we should make it possible to query quotas over NFSv4 as well.2 KB (306 words) - 21:03, 1 April 2021