Sponsored Content
Operating Systems HP-UX Is it really impossible to force umount on HP-UX Post 302315066 by vbe on Monday 11th of May 2009 11:21:01 AM
Old 05-11-2009
you are in / arent you when you type fuser?
If it is trying (as it seems) I supect you have also an issue with the NFS server:
to make sure rpc.statd and rpc.lockd are available and responding to RPC requests:
Code:
/usr/bin/rpcinfo -u servername status
/usr/bin/rpcinfo -u servername llockmgr
/usr/bin/rpcinfo -u servername nlockmgr
/usr/bin/rpcinfo -u clientname status
/usr/bin/rpcinfo -u clientname llockmgr
/usr/bin/rpcinfo -u clientname nlockmgr

If any of these commands returns RPC_TIMED_OUT, the rpc.statd or rpc.lockd process may be
hung.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

umount

:confused: Twofold question for you unix "guru's" 1) When attempting to use the umount command I get a message stating that the partition that I want to unmount is busy. Is there another command that I need to use prior to the umount command to clear the partition of activity????? ... (2 Replies)
Discussion started by: rod23
2 Replies

2. UNIX for Dummies Questions & Answers

umount error

the program as follow: mount /dev/fd0135ds18 /mnt cd /mnt touch file1 cat /file2 >/mnt/file1 umount /dev/fd135ds18 when error tell device busy could you tell me the reason? (1 Reply)
Discussion started by: fresh
1 Replies

3. UNIX for Advanced & Expert Users

umount help

hi all, I inherit a Solaris7 system with /home mounted via a share from the NFS server. When I look at mnttab, there are two entries mounted under /home. Let's say they are server:/home/a and server:/home/b. I would like to maintain /home/a but not /home/b. However, I just don't know where... (4 Replies)
Discussion started by: andrec
4 Replies

4. Solaris

umount is failing

I am trying to umount a NFS share. When I do the following: # umount syrupg21 umount: /oebs/syrupg21: device is busy device bussy so I like to check what is working on the system.... # fuser -muv /oebs/syrupg21/ # So no locks should be there... any clue? Regards, Johan... (3 Replies)
Discussion started by: suntac
3 Replies

5. Solaris

force umount in solaris 2.6

Hi All, Can someone share with me how to force umount in solaris 2.6? Thanks Leong (3 Replies)
Discussion started by: bkleong
3 Replies

6. UNIX for Dummies Questions & Answers

Almost impossible question

Would anyone know how to get a directory listing of all files in a directory as well as all the files in their respective subdirectories and save the listings to a file? I realize this is tricky. (12 Replies)
Discussion started by: danceofillusion
12 Replies

7. UNIX for Dummies Questions & Answers

Next to impossible question

I noticed that I have a print job that is hung up (lpstat -o) due to a broken printer. Is there a way to re-route the printed information into a text file? Or does it exist somewhere in UNIX as a text file? (5 Replies)
Discussion started by: danceofillusion
5 Replies

8. HP-UX

how to force umount

sorry, wrong section, mod please close thread (0 Replies)
Discussion started by: robertngo
0 Replies

9. UNIX for Advanced & Expert Users

fsck.gfs2 outputs "RG recovery impossible; I can't fix this file system"

I have a CentOS release 5.2 (Final)host running kernel 2.6.18-92.el5 with at raid 10 that had two mirrored drives fail. The drives were re-inserted and now the raid shows healthy (for now). I tried to mount but got an Input/output error. I then attempted a fsck: fsck.gfs2 -y /dev/vg_01/uss_vol... (0 Replies)
Discussion started by: king_hippo
0 Replies

10. Solaris

Impossible to access on /vol1

hi team, I'm a new with Solaris system and i'm a french, so my english will not be very good but I'll try to explain my problem. I have a Sun server SunFire X4170 with Solaris 10 as OS. since last week I am not able to access on /vol1 anymore. And bellow are the warning messages which are... (20 Replies)
Discussion started by: cerco
20 Replies
RPC.LOCKD(8)						    BSD System Manager's Manual 					      RPC.LOCKD(8)

NAME
rpc.lockd -- NFS file locking daemon SYNOPSIS
rpc.lockd [-d debug_level] [-g grace_period] [-x host_monitor_cache_period] DESCRIPTION
The rpc.lockd utility provides monitored and unmonitored file and record locking services in an NFS environment. To monitor the status of hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8). The rpc.lockd utility runs whenever its services are needed to support either the NFS server (see nfsd(8)) or the NFS client (an NFS file system on which file locking requests have been made). The daemon will remain running until a short time after its services are no longer needed to support either the NFS client or NFS server. rpc.lockd will also make sure that the statd service (on which it depends) is run- ning. The following is a list of command line options that are available. However, since rpc.lockd is normally started by launchd(8), configura- tion of these options should be controlled using the equivalent settings in the NFS configuration file. See nfs.conf(5) for a list of tun- able parameters. -d The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are logged with level LOG_DEBUG and facility LOG_DAEMON. Specifying a debug_level of 1 results in the generation of one log line per protocol operation. Higher debug levels can be specified, causing display of operation arguments and internal operations of the dae- mon. -g The -g option allows to specify the grace period (in seconds). During the grace period rpc.lockd only accepts requests from hosts which are reinitialising locks which existed before the server restart. Default is 45 seconds. -x The -x option tells rpc.lockd how long to cache state records for monitored hosts. Setting it to zero will disable the cache which will make lock and unlock requests from a single client more expensive because of additional interaction with the client's statd. The default cache time is 60 seconds. Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON. FILES
/var/run/lockd.pid The pid of the current lockd daemon. /System/Library/LaunchDaemons/com.apple.lockd.plist The lockd service's property list file for launchd(8). /usr/include/rpcsvc/nlm_prot.x RPC protocol specification for the network lock manager protocol. SEE ALSO
nfs.conf(5), rpc.statd(8), syslog(3), launchd(8) BUGS
The current implementation serialises locks requests that could be shared. STANDARDS
The implementation is based on the specification in "Protocols for X/Open PC Interworking: XNFS, Issue 4", X/Open CAE Specification C218, ISBN 1 872630 66 9. HISTORY
A version of rpc.lockd appeared in SunOS 4. BSD
January 9, 2007 BSD
All times are GMT -4. The time now is 03:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy