This post is more than 5 years old
26 Posts
0
3013
nsrmmd associations
Hi,
we have four tape drives cpnnect to the backup server and OS path are /dev/rmt/112stcbn,/dev/rmt/113stcbn and /dev/rmt/42stcbn. All the devices are working fine.How do we know which device is using which nsrmmd?. Is there way we could map the nsrmmd process through to its /dev/rmt
ps -ef | grep nsrmmd
/usr/sbin/nsrmmd -n 57
/usr/sbin/nsrmmd -n 55
/usr/sbin/nsrmmd -n 10
Any suggestion?
coganb
736 Posts
0
October 18th, 2012 03:00
Hi,
Run the 'fuser' command against the device path and this will give you the process id of the nsrmmd process that is handling that device.
-Bobby
coganb
736 Posts
0
October 18th, 2012 05:00
I'm not sure - why would you want to do that?
-Bobby
Rajesh Sekar
26 Posts
0
October 18th, 2012 05:00
.
Thanks Bobby.It is very useful. However it is giving the information about the pid when the drive is writing the data and not for the idle ones.Is there a way we can pid for the idle one's also.
bash-3.00$ /usr/sbin/fuser /dev/rmt/0stcbn
/dev/rmt/0stcbn: 25396o
bash-3.00$ /usr/sbin/fuser /dev/rmt/14stcbn
/dev/rmt/14stcbn:
ps -ef | grep nsrmmd /usr/sbin/nsrmmd -n 57 /usr/sbin/nsrmmd -n 55 /usr/sbin/nsrmmd -n 10
mridul_singh
57 Posts
0
October 18th, 2012 05:00
Whne the device is not in use, none of the nsrmmd is associated with any device. The association happens only when the drive is in use. This is the reason you will not get a pid for the idle devices.
ble1
14.3K Posts
0
October 18th, 2012 07:00
That's not correct - at least not for all versions up to NW8. I know NW8 had changes in respect to nsrmmd and how it is inwoked, but not many have gone boldly where no men has gone before... Were you referring to NW8 perhaps?
Rajesh Sekar
26 Posts
0
October 18th, 2012 20:00
Nope.It is Networker 7.6.2.Sometimes we have issues with the particular drives.From the NMC we know which tape drive is causing but we don't know which nsrmmd is associated to that drive,if we know that, we can kill that particular nsrmmd rather bouncing the services and bring it online.(backup server or on the storage node).It looks be fine when the drive is wirting the data,fuser works fine and not the other devices which is idle.
Anyways it is not best pratice to kill the nsrmmd with knowing the root cause but still wanted to check is there a way we can get the associations?
Once again thanks to Bobby,Crvelin and Mridul for your help.