ADSM-L

Re: Device locking danger.

2002-06-25 18:31:20
Subject: Re: Device locking danger.
From: Michael Benjamin <MBenjamin AT BUNNINGS.COM DOT AU>
Date: Wed, 26 Jun 2002 06:29:18 +0800
We've also had drives marked as completely unavailable on occasion when the
server cannot get around such a lock. Something else to watch out for. q
drive f=d to
check the status.

> -----Original Message-----
> From: Zlatko Krastev/ACIT [SMTP:acit AT ATTGLOBAL DOT NET]
> Sent: Tuesday, June 25, 2002 7:37 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Device locking danger.
>
> And have in mind that someone can do it also from ANY MgSysSAN node !!
> Thus it would be good to disable 'configure' method for smcN on Storage
> Agent systems to prevent device become "Available" and be used from that
> box's administrator causing grief to you at the server box.
>
> Zlatko Krastev
> IT Consultant
>
>
>
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> To:     ADSM-L AT VM.MARIST DOT EDU
> cc:
>
> Subject:        Device locking danger.
>
> Please note, this may be common knowledge to some of you but I thought I'd
> mention it again.
>
> TSM Server can have problems if you are accessing a device like /dev/rmtX
> or
> a SCSI media changer
> /dev/smc0 with tapeutil. You will see in the actlog the server is unable
> to
> access the device as you
> have already initiated an exclusive lock on the device.
>
> Therefore, if you are going to do tapeutil procedures or anything else
> that
> accesses/queries the devices,
> do so when the server is inactive, and DO check it's health afterward and
> the actlog for error messages.
>
> We've seen this occur ourselves a couple of times now on TSM 4.2.2.0
>
> Comments?
>
> **************************************************************************
> Bunnings Legal Disclaimer:
>
> 1)      This document is confidential and may contain legally privileged
>         information. If you are not the intended recipient, you must not
>                                                   disclose or use the
> information contained in it. If you have
>         received this e-mail in error, please notify us immediately by
>         return email and delete the document.
>
> 2)      All e-mails sent to and sent from Bunnings Building Supplies are
>         scanned for content. Any material deemed to contain inappropriate
>         subject matter will be reported to the e-mail administrator of
>         all parties concerned.
>
> **************************************************************************

**************************************************************************
Bunnings Legal Disclaimer:

1)      This document is confidential and may contain legally privileged
        information. If you are not the intended recipient, you must not        
                                                disclose or use the information 
contained in it. If you have
        received this e-mail in error, please notify us immediately by
        return email and delete the document.

2)      All e-mails sent to and sent from Bunnings Building Supplies are
        scanned for content. Any material deemed to contain inappropriate
        subject matter will be reported to the e-mail administrator of
        all parties concerned.

**************************************************************************
<Prev in Thread] Current Thread [Next in Thread>