Error Help Stale Nfs File Handle

Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by how to fix stale nfs file handle error Red Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack stale nfs file handle solaris Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift mount.nfs: stale nfs file handle Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red

Stale Nfs File Handle Autofs

Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application stale nfs file handle redhat Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Regi

Selection Strategies My IP Address RAID Analysis Tool Archives November 2015 October 2015 May 2015 March 2015 February 2015 January 2015 December 2014 November 2014 September 2014 August 2014 July 2014 June 2014 May 2014 March 2014 February 2014 January 2014 December 2013 November 2013 October 2013 stale nfs file handle ubuntu September 2013 May 2013 February 2013 January 2013 October 2012 September 2012 August 2012 June

Stale Nfs File Handle Netapp

2012 April 2012 March 2012 February 2012 January 2012 November 2011 October 2011 Meta Register Log in Entries RSS Comments RSS WordPress.org How to

Stale Nfs File Handle Docker

fix stale NFS mounts on linux without rebooting I have often noticed that some folks reboot systems to fix stale NFS mount problems which can be disruptive. Fortunately, that often isn't necessary. All you have to do is restart https://access.redhat.com/solutions/2674 nfs and autofs services. However that sometimes fails because user processes have files open on the stale partition or users are cd'ed to the stale partition. Both conditions are easy to fix. The steps to fix stale mounts by addressing the previously described conditions are described below. Step 1. Kill process with open files on the partition Use lsof to find the processes that have files open on the partition and then kill those processes using kill or pkill. http://joelinoff.com/blog/?p=356 Step 1. Kill Processes Shell % sudo su - % # Find the jobs that are accessing the state partition and kill them. % kill -9 $(lsof |\ egrep '/stale/fs|/export/backup' |\ awk '{print $2;}' |\ sort -fu ) % # Restart the NFS and AUTOFS services % service nfs stop % service autofs stop % service nfs start % service autofs start % # Check it % ls /stale/fs 12345678910111213141516171819202122232425 % sudo su - % # Find the jobs that are accessing the state partition and kill them.% kill -9 $(lsof |\egrep '/stale/fs|/export/backup' |\awk '{print $2;}' |\sort -fu ) % # Restart the NFS and AUTOFS services% service nfs stop% service autofs stop% service nfs start% service autofs start% # Check it% ls /stale/fs Typically this is sufficient but if it fails, you need to go to step 2. Step 2. Kill process that have cd'ed to the partition Look at the current working directory of all of the users. If any of them are on the partition, that process has to be killed. Step 2. Kill Specific Users Shell % sudo su - % # List the users that are cd'ed to the stale partition and kill their jobs. % # NOTE: change /stale/fs to the path to your stale partition. % kill -9 $( for u in $( who | awk '{print $1;}' | sort -fu ) ; do \ pwdx $(pgre

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://serverfault.com/questions/617610/stale-nfs-file-handle-after-reboot about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to stale nfs the top “Stale NFS file handle” after reboot up vote 12 down vote favorite 6 On the server node, it is possible to access an exported folder. However, after reboots (both server and client), the folder is no longer accessible from the clients. On server # ls /data Folder1 Forlder2 and the /etc/exports file contains /data 192.168.1.0/24(rw,no_subtree_check,async,no_root_squash) On client # ls /data ls: cannot access /data: Stale NFS file handle stale nfs file I have to say that there were no problem with the shared folder from client side however after reboots (server and client), I see this message. Any way to fix that? nfs linux-networking mount share|improve this question asked Aug 3 '14 at 18:16 mahmood 2874716 add a comment| 2 Answers 2 active oldest votes up vote 13 down vote accepted The order of reboots is important. Rebooting the server after the clients can result in this situation. The stale NFS handle indicates that the client has a file open, but the server no longer recognizes the file handle. In some cases, NFS will cleanup its data structures after a timeout. In other cases, you will need to clean the NFS data structures yourself and restart NFS afterwards. Where these structures are located are somewhat O/S dependent. Try restarting NFS first on the server and then on the clients. This may clear the file handles. Rebooting NFS servers with files opened from other servers is not recommended. This is especially problematic if the open file has been deleted on the server. The server may keep the file open until it is rebooted, but the reboot will remove the in-memory file handle on the server side. Then the client