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:
If any of these commands returns RPC_TIMED_OUT, the rpc.statd or rpc.lockd process may be
hung.
: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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT MOJAVE
rpc.lockd
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