[Fwd: device database locked by cluster member]

From: Mike Broderick (broderic@MIT.EDU)
Date: 04/24/03

  • Next message: Mike Broderick: "device database locked by cluster member" 
    Date: Thu, 24 Apr 2003 17:01:20 -0400
From: Mike Broderick <broderic@MIT.EDU>
To: tru64-unix-managers <tru64-unix-managers@ornl.gov>

      One more seemingly inportant thing. This is a standalone (5.1a+pk1)
    system (no cluster). _Mike

    -------- Original Message --------
    Subject: device database locked by cluster member
    Date: Thu, 24 Apr 2003 16:59:24 -0400
    From: Mike Broderick <broderic@mit.edu>
    To: tru64-unix-managers <tru64-unix-managers@ornl.gov>

    I get this message trying to access the device db:

    # dsfmgr -s
    dsfmgr: NOTE: waiting for Session Lock held by member #0. At Thu Apr 24
    16:53:41 2003
    ^C
    #

    We were trying to clean up an old device earlier but these two hwmgr
    commands just hung (not kill-able):

    # ps -ef | grep hwmgr | grep -v grep
    root 397765 397719 0.0 15:53:02 pts/1 0:00.10 hwmgr sc sc
    root 398377 397758 0.0 16:00:48 pts/2 0:00.04 hwmgr delete
    scsi -did 17
    #

    The device being deleted above is in a strange state:

    # hwmgr sh sc | grep 17
      109: 17 pine tape none 0 1 tape113
    # hwmgr sh sc -id 109 -full

            SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
     HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
    -------------------------------------------------------------------------
      109: 17 pine tape none 0 1 tape113

          WWID:06100036:"QUANTUM DLT7000 :d01l00034:1000-00e0-0201-a2d1"

          BUS TARGET LUN PATH STATE
          ------------------------------
          5 8 34 stale

    # hwmgr sh comp -id 109 -full

     HWID: HOSTNAME FLAGS SERVICE COMPONENT NAME
    -----------------------------------------------
      109: pine rcd-i iomap SCSI-WWID:06100036:"QUANTUM
    DLT7000 :d01l00034:1000-00e0-0201-a2d1"

      DSF GROUP
      INSTANCE GRPFLAGS GROUPID SUBSYSTEM BASENAME L1 L2
      ---------------------------------------------------------
      0 40 54 cam_tape tape113 tape (null)

      DEVICE NODE
      ID LBdevT LCdevT CBdevT CCdevT BFlags CFlags Class Suffix
    L3B L3C
      
    -------------------------------------------------------------------------------
      16 0 330045e 0 1300307 0x0 0x861 0x0
     . . .
      15 0 330044f 0 130031a 0x0 0x861 0x0 _d7
    (null) norewind

      COMPONENT INCONSISTENCY
      -----------------------
      Cluster shared component has no entry in the cluster database.

    How can I clear this up w/o rebooting? Is there a lock file or
    something somewhere I can delete?

                                                          _Mike

  • Next message: Mike Broderick: "device database locked by cluster member"

    Relevant Pages

    • Summary: 5.1B pk3 cluster FS and file atimes
      ... > access time stamp. ... one cluster member will see a different atime than the other. ... > the file sees the correct atime, but the other member (which is the CFS ... when one cluster member had to generate an internal partial ...
      (Tru64-UNIX-Managers)
    • SUMMARY: Configuring a TRU64 Host as Router.
      ... cluster node as the gateway [as the cluster members are directly connected ... Add the route for 129.* ip in the hosts of private network ... Configuring a TRU64 Host as Router. ... the cluster member HOSTA. ...
      (Tru64-UNIX-Managers)
    • Re: PID creation in a cluster
      ... The format of a PID is not documented, but as it currently exists goes ... The highest bits are a unique cluster value. ... There are MAXPROCESSCNT 'slots', or processes that can exist at one time. ... the upper bits will be nonzero for a cluster member and will be unique ...
      (comp.os.vms)
    • Re: Cluster vote allocation question
      ... >> When selecting the optimal subset of nodes to survive after a loss of ... "If a cluster member is shut down or fails, ... I've submitted a suggestion to the documentation folks to improve this ...
      (comp.os.vms)