Networker

Re: [Networker] Antw: RE: [Networker] verify label problem (NW7.1.2 & AS 2SR3)

2004-07-20 11:55:06
Subject: Re: [Networker] Antw: RE: [Networker] verify label problem (NW7.1.2 & AS 2SR3)
From: Chad Smykay <csmykay AT RACKSPACE DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 20 Jul 2004 10:54:46 -0500
This is what I do to find the device an nsrmmd process is using on a RedHat
Linux Server.

Run:

 ps auxw | grep nsrmmd

root     19659  0.5  0.0  5324 2560 ?        S<   Jul17  21:36
/usr/sbin/nsrmmd -n 2
root     19662  0.0  0.0  4300 1508 ?        S<   Jul17   0:00
/usr/sbin/nsrmmd -n 3
root     19658  0.1  0.0  6436 3328 ?        S<   Jul17   6:04
/usr/sbin/nsrmmd -n 1
                |
Grab the process ID and go into it's running directory in the /proc dir.  So
for instance if I wanted to look at "/usr/sbin/nsrmmd -n 1" then I would cd
into:

 cd /proc/19658/

Next go into the "fd" directory.  If you do an:

 cd fd/
 ls -la

You should see something like this:

l-wx------    1 root     root           64 Jul 20 10:52 0 ->
/nsr/logs/daemon.log
l-wx------    1 root     root           64 Jul 20 10:52 1 ->
/nsr/logs/daemon.log
lrwx------    1 root     root           64 Jul 20 10:52 10 -> /dev/nst1
l-wx------    1 root     root           64 Jul 20 10:52 2 ->
/nsr/logs/daemon.log
lrwx------    1 root     root           64 Jul 20 10:52 3 -> /dev/null
lrwx------    1 root     root           64 Jul 20 10:52 4 -> /dev/null
lrwx------    1 root     root           64 Jul 20 10:52 5 ->
socket:[158000353]
lrwx------    1 root     root           64 Jul 20 10:52 6 ->
socket:[158000361]
lrwx------    1 root     root           64 Jul 20 10:52 7 ->
socket:[158004653]
lrwx------    1 root     root           64 Jul 20 10:52 8 ->
socket:[158004654]
lrwx------    1 root     root           64 Jul 20 10:52 9 ->
socket:[158006972]

As you can see this process is accessing my /dev/nst1 drive.

This information is ONLY useful on Linux servers and I am running RH AS 2.1
in my environments.  If someone can respond back with any equivalents for
Sun that would be great.

Thanks,


Chad Smykay, RHCE, LCNA
Systems Storage Administrator
Rackspace Managed Hosting (TM) - The Managed Hosting Specialist (TM)
210-892-4025 ext 1603
Cell: 210-273-2344

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] 
On
Behalf Of Spindler, Brian
Sent: Tuesday, July 20, 2004 9:22 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Antw: RE: [Networker] verify label problem (NW7.1.2
& AS 2SR3)

Can you display the parameters used with the command (i.e. pslist ??
<PROCNAME>) that you can get the tape drive to display?
Thanks,
Brian

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Fowler, Carter
Sent: Tuesday, July 20, 2004 8:54 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Antw: RE: [Networker] verify label problem
(NW7.1.2 & AS 2SR3)

There is a program called "process explorer" that you can obtain from
www.sysinternals.com and if you have a look for the nsrmmd.exe process, it
will show you in the details what tape drive it's using.  We use within our
win2k environment to kill 'stuck' devices from time to time.

Hope this helps!

Cheers,

Carter Fowler
Hardware Services Technician
Technology Services Division
600 - 380 Wellington St.
London, ON, CA, N6A 5B5
Off: 519.661.5711
Fax: 519.661.5408
Cel: 519.870.4956
cfowler AT london DOT ca


 -----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT listmail.temple DOT edu]
On Behalf Of Thorsten Linow
Sent: July 20, 2004 1:44 AM
To: NETWORKER AT listmail.temple DOT edu
Subject: Antw: RE: [Networker] verify label problem (NW7.1.2 & AS 2SR3)

Hi Chad,

Well that's exactly what I have. I was just wondering if there is an easier
way to figure out the hanging nsrmmd.
Your experience with Alphastor sounds not so good, any comment?

Regards, Thorsten Linow

UNIX SYS-Admin; Backup & Recovery
Talkline GmbH & CO KG
See You @ www.talkline.de


>>> "Chad Smykay" <csmykay AT rackspace DOT com> 19.07.04 18:49:18 >>>
I used to see this issue all the time when we "used" to have AlphaSnor.
When it happened we just found the offending nsrmmd process and killed it.
To find the offending nsrmmed process.....well that is another story.
Best
bet is to do an strace on all of the nsrmmd processes (if you are running a
*nix) and kill any of the processes that are not doing anything.  Nsrd will
notice that they died off and automagically start them back up again.

Regards,


Chad Smykay, RHCE, LCNA
Systems Storage Administrator


-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On
Behalf Of Carl Farnsworth
Sent: Friday, July 16, 2004 10:01 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] verify label problem (NW7.1.2 & AS 2 SR3)

I wish I could read Hrvoje's response, but ...
1.  I don't think you can use the -H option for a single drive.
2.  Maybe Solaris behaves better than Windows, but it's been my experience
(since 6.1.3) that a hung nsrjb process will block any successive nsrjb
commands.  Try to find the "nsrjb -l ..." process that was trying to mount
the volume and kill it.
3.  In an AlphaStor environment, the "nsrjb -H" command doesn't actually
reset the jukebox, just tries to re-sync slot status with AlphaStor.
Use "nsrjb -HHv" to get NetWorker to realize that the drives have been
unloaded.  Unfortunately, this will interrupt any other backups in progress.
4.  Stopping and re-starting NetWorker services may have the same effect,
but you shouldn't have to delete and re-create the device.

HTH
cf

On Thu, 15 Jul 2004 09:36:12 +0200, Thorsten Linow
<Linow.Thorsten AT TALKLINE DOT DE> wrote:

>Hi,
>We're running Networker 7.1.2 and Alphastor 3 SR2 together on on Sun
>V880
Server.
>Our STK9840 tapedrives are connected via SAN and controlled by ACSLS.
>The bunch of STK9840 Tapedrives are configuerd as
>smartmedia-jukebox_9840
in networker
>another bunch of STK9940B Tapedrives are configured as smartmedia-
jukebox9940 in Networker
>Now we have a logical 9840 drive in the networker GUI having the status
verify label.
>-The volume is clearly mounted in Alphastor and in ACSLS.
>-The status inside the networker GUI is verify label and a "mt -
f /dev/rmt/7cbn  status " shows me a mounted tape.
>-The tape is not unloadable by networker.
>-asvolunmount will sucessfully unmount the alphastor and acsls device
>but
not the logical networker device.
>-Setting the drive into servicemode wouldn't help.
>-"mt -f /dev/rmt/7cbn release" or "mt -f /dev/rmt/7cbn offline wouldn't
clear the loaded slots, loaded barcode and loaded volume entries
>  for the logical device inside the (smartmedia-)jukebox inside
> networker-
GUI.
>-deleting the enties in loaded slots, loaded barcodes and loaded
>volumes
for the coresponding logical drive inside the jukebox-configuration is not
allowed anymore
>  since NW7.1.2
>-"nsrjb -vvvH f drive98_40" takes houres without sucess.
>
>Any sugestions else than delete and create logical drive in networker
>or
restarting networker?
>
>Thank's in advance & kind Regards Thorsten Linow

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=