I believe I've seen similar when the node was renamed.  At least in a Windows 
environment.

The filespaces were ID'd with the former name.

Maybe a backup did run?

------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - DISC
Harold.Vandeventer AT da.ks DOT gov
(785) 296-0631


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray/AC/VCU
Sent: Monday, July 18, 2011 12:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Filespaces appearing for nodes that have never backed up

Recently, I was asked to delete 2-nodes that were accidentally defined and
never used.  When I tried to remove the node, it said "filespaces exist"

When I do a "q filespace", it returns info for a completely different
node:

1:12:27 PM   SUN : q filespace persimmon.vcu.edu
Node Name       Filespace   FSID Platform Filespace Is Files-    Capacity
Pct
                Name                      Type        pace           (MB)
Util
                                                    Unicode?
--------------- ----------- ---- -------- --------- --------- -----------
-----
PERSIMMON.VCU.- WALNUT.DOM-    1 (?)      API:Domi-    No             0.0
0.0
 EDU             DBS                       noData


This has me concerned that I have some kind of database corruption?

To further feed my paranoia, when I d a query on the node, I get:
1:15:08 PM   SUN : q node persimmon.vcu.edu f=d
                     Node Name: PERSIMMON.VCU.EDU
                      Platform: (?)
               Client OS Level: (?)
                Client Version: (?)
            Policy Domain Name: NOTES
         Last Access Date/Time: 04/11/2011 11:39:48
        Days Since Last Access: 98
        Password Set Date/Time: 04/11/2011 11:42:52
       Days Since Password Set: 98
         Invalid Sign-on Count: 0
                       Locked?: No
                       Contact: Marie Scott
                   Compression: Client
       Archive Delete Allowed?: Yes
        Backup Delete Allowed?: Yes
        Registration Date/Time: 04/11/2011 11:39:48
     Registering Administrator: ZFORRAY
Last Communication Method Used:
   Bytes Received Last Session: 0
       Bytes Sent Last Session: 0
      Duration of Last Session: 0.00
   Pct. Idle Wait Last Session: 0.00
  Pct. Comm. Wait Last Session: 0.00
  Pct. Media Wait Last Session: 0.00
                     Optionset:
                           URL:
                     Node Type: Client
    Password Expiration Period: 0 Day(s)
             Keep Mount Point?: No
  Maximum Mount Points Allowed: 1
        Auto Filespace Rename : No
             Validate Protocol: No
                   TCP/IP Name:
                TCP/IP Address:
            Globally Unique ID:
         Transaction Group Max: 0
               Data Write Path: ANY
                Data Read Path: ANY
            Session Initiation: ClientOrServer
            High-level Address: 128.172.184.1
             Low-level Address: 1501
        Collocation Group Name:
              Proxynode Target:
               Proxynode Agent:
                   Node Groups:
                 Email Address:
                 Deduplication: ServerOnly
                Client OS Name:
 Client Processor Architecture:
         Client Target Version: (?)

Note that almost everything is blank, as it should be.  However, the
"High-level Address" is not a valid IP address/not assigned to anything.
So where did it get this info from?


Any ideas what could be going on?  This is a 6.2.2.0 server on RH Linux.
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html