It seems like nsrmmd keeps a drive unavailable, without any reason. This
probably happens after a backup job finishes. However, I can't seem to be
able to figure out what causes this. No jobs are running, and there are no
savesets waiting to be backed up. There are no pending media requests. The
drive still sits in the state "ready for writing, idle". An attempt to
unmount the drive makes the server claim that the drive is busy. I can't
see any rouge savegrp processer or similar.

My investigation shows this:

[root@britt:/] fuser /dev/rmt/9cbn
/dev/rmt/9cbn:      587o

[root@britt:/] ps -ef |grep 587
    root   587   245  0 18:30:35 ?        7:05 /usr/sbin/nsrmmd -n 4

[root@britt:/] ps -ef |grep nsrmmd
    root   583   245  0 18:30:30 ?       30:51 /usr/sbin/nsrmmd -n 1 -r 
britt.qbranch.se
    root   499   245  0 18:30:04 ?        1:28 /usr/sbin/nsrmmdbd
    root   586   245  0 18:30:33 ?       51:06 /usr/sbin/nsrmmd -n 3
    root   587   245  0 18:30:35 ?        7:05 /usr/sbin/nsrmmd -n 4
    root   585   245  0 18:30:32 ?       39:44 /usr/sbin/nsrmmd -n 2
    root   588   245  0 18:30:37 ?       32:12 /usr/sbin/nsrmmd -n 5
    root   589   245  0 18:30:39 ?       11:03 /usr/sbin/nsrmmd -n 6
    root  1199   245  0 02:10:32 ?        0:00 /usr/sbin/nsrmmd -n 7

So, its the nsrmmd process with instance number 4 that is keeping the
drive open. The number of nsrmmd processes seems normal to me, since the
server has 6 drives attached. However, one drive is dedicated to
SnapImage/NDMP useage.

Problem environment:

SunOS britt 5.7 Generic_106541-21 sun4u sparc SUNW,Ultra-4
NetWorker 6.1.3 with patch for nsrjb race condition.

Ideas, anyone?

//Oscar

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=