|
Re: [ADSM-L] Move node to new domain
2013-08-20 12:06:17
No orphaned filespaces
Tim
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sheridan, Peter T.
Sent: Tuesday, 20 August, 2013 11:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Move node to new domain
Another wild guess and doubt it will matter but if you do q filespace on the
node do u see orphaned filespaces that you might be able to delete and clean
things up ?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT vm.marist DOT edu] On Behalf Of
Tim Brown
Sent: Tuesday, August 20, 2013 10:55 AM
To: ADSM-L AT vm.marist DOT edu
Subject: Re: [ADSM-L] Move node to new domain
Yes still seeing orphaned references
Tim
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Ehresman,David E.
Sent: Tuesday, 20 August, 2013 11:31 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Move node to new domain
Tim,
Have you done an "audit vol XXX fix=yes" on the volumes in question? That
should fix discrepancies between TSM tables
David
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nick Laflamme
Sent: Tuesday, August 20, 2013 11:07 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Move node to new domain
The most alarming thing I see about Tim's question is the discrepancy between Q
NODEDATA and Q CONTENT. Q NODEDATA says that there's data for that user in that
volume; Q CONTENT contradicts that. He doesn't show the full output of the Q
CONTENT command, but if what he says is true, I'd suggest he open a PMR.
Note that none of that has anything to do with changing which policy domain a
node is assigned to. :-)
Nick
2013/8/20 Tim Brown <TBrown AT cenhud DOT com>
> I am having difficulty sending to adsm-l so if you already got this
> please ignore!
>
>
>
>
>
> We recently moved a node from domain dm1 to domain dm2 but are still
> seeing nodedata references in dm1 that we cant remove.
>
>
>
> If we issue Q CONTENT D:\DM1_PRIM1\0001EAD4.BFS > 0001EAD4.TXT
> theres not any references to node NODE1 in the resulting txt file.
>
>
>
> How can we resolve this ?
>
>
>
> Q NODEDATA NODE1
>
>
>
> Node Name Volume Name Storage Pool
> Physical
>
> Name
> Space
>
>
> Occupied
>
>
> (MB)
>
> ---------------- ------------------------------ ----------------
> --------
>
>
>
>
>
> NODE1 D:\DM1_PRIM1\0001EAD4.BFS DM1_PRIM
> 0.02
>
> NODE1 D:\DM1_PRIM2\000165B3.BFS DM1_PRIM
> 0.11
>
> NODE1 D:\DM1_PRIM2\0001EA8D.BFS DM1_PRIM
> 128.83
>
>
>
> NODE1 M:\DM2_PRIM1\00017F02.BFS DM2_PRIM
> 11,138.03
>
> NODE1 M:\DM2_PRIM1\000180C5.BFS DM2_PRIM
> 148.23
>
> NODE1 M:\DM2_PRIM1\000180C6.BFS DM2_PRIM
> 889.02
>
> NODE1 M:\DM2_PRIM1\000180C7.BFS DM2_PRIM
> 434.84
>
> NODE1 M:\DM2_PRIM1\000184AD.BFS DM2_PRIM
> 1,070.09
>
> NODE1 M:\DM2_PRIM1\000184B5.BFS DM2_PRIM
> 0.45
>
> NODE1 M:\DM2_PRIM1\00018A84.BFS DM2_PRIM
> 294.61
>
> NODE1 M:\DM2_PRIM1\00019714.BFS DM2_PRIM
> 918.17
>
> NODE1 M:\DM2_PRIM1\00019785.BFS DM2_PRIM
> 413.25
>
> NODE1 M:\DM2_PRIM1\00019C9D.BFS DM2_PRIM
> 531.94
>
> NODE1 M:\DM2_PRIM1\0001A9D5.BFS DM2_PRIM
> 527.01
>
> NODE1 M:\DM2_PRIM1\0001B9F8.BFS DM2_PRIM
> 510.82
>
> NODE1 M:\DM2_PRIM1\0001BB2B.BFS DM2_PRIM
> 1,555.39
>
> NODE1 M:\DM2_PRIM1\0001BB2C.BFS DM2_PRIM
> 324.95
>
> NODE1 M:\DM2_PRIM1\0001BF76.BFS DM2_PRIM
> 1,029.69
>
> NODE1 M:\DM2_PRIM1\0001CA6A.BFS DM2_PRIM
> 816.66
>
> NODE1 M:\DM2_PRIM1\0001D165.BFS DM2_PRIM
> 331.11
>
> NODE1 M:\DM2_PRIM1\0001DE62.BFS DM2_PRIM
> 1,141.98
>
> NODE1 M:\DM2_PRIM1\0001E9B9.BFS DM2_PRIM
> 67.84
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Tim Brown
>
> Supervisor Computer Operations
>
> Central Hudson Gas & Electric
>
|
|
|
