[CentOS] nfs stuck, don't know what processes to kill

Wed Feb 3 17:55:14 UTC 2016
Dave Burns <tburns at hawaii.edu>

Thanks. How did I miss that -l switch? Unfortunately, I went into panic
mode and just rebooted, but I'll know next time.
Dave

On Tue, Feb 2, 2016 at 9:00 AM, Phelps, Matthew <mphelps at cfa.harvard.edu>
wrote:

> Try "umount -fl"            ('eff el')
>
> On Tue, Feb 2, 2016 at 1:58 PM, Dave Burns <tburns at hawaii.edu> wrote:
>
> > My NFS server is up and other clients can access x. One particular client
> > can't. I tried to unmount the NFS share:
> >
> > [root at nfsclient ~]#  umount -f /disk/x
> > umount2: Device or resource busy
> > umount.nfs: /disk/x: device is busy
> > umount2: Device or resource busy
> > umount.nfs: /disk/x: device is busy
> >
> > If I use df or lsof to try to figure out what process to kill, they
> hang. I
> > am reluctant to just reboot, as many other users are getting stuff done.
> > dmesg doesn't show anything useful.
> >
> > How to get unstuck?
> >
> > thanks,
> > Dave
> > _______________________________________________
> > CentOS mailing list
> > CentOS at centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
>
>
>
> --
> Matt Phelps
> System Administrator, Computation Facility
> Harvard - Smithsonian Center for Astrophysics
> mphelps at cfa.harvard.edu, http://www.cfa.harvard.edu
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



-- 
This email is:    [ ] request action  [ ] request info   [x] fyi        [ ]
social
Response needed:  [ ] yes          [x] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [x] none
http://www.43folders.com/2005/09/19/writing-sensible-email-messages