Backup Central

This is on a RHEL 5.7 x86_64 system; an old stgpool volume on external storage failed, so I marked it "destroyed", and then tried to run

del vol /the/volume/name discarddata=yes

That fails with

ANR2017I Administrator ADMIN issued command: DELETE VOLUME /TSM_POOL/19/data19
discarddata=yes
ANR0984I Process 1836 for DELETE VOLUME (DISCARD DATA) started in the
BACKGROUND at 01:19:56 PM.
ANR2222I Discard Data process started for volume /TSM_POOL/19/data19 (process
ID 1836).
ANR9999D_2990890315 PrepareClusters(dftxn.c:875) Thread<22998>: Logical
occupancy went negative for Pool 25, Ck1=75, Ck2=1.
ANR9999D Thread<22998> issued message 9999 from:
ANR9999D Thread<22998> 0x00000000b95ba2 OutDiagToCons
ANR9999D Thread<22998> 0x00000000b986a9 outDiagfExt
ANR9999D Thread<22998> 0x00000000610e01 DfPrepareTxn
ANR9999D Thread<22998> 0x000000005e05a1 bfPrepareTxn
ANR9999D Thread<22998> 0x00000000b682c1 CollectVotes
ANR9999D Thread<22998> 0x00000000b686b4 tmEnd
ANR9999D Thread<22998> 0x000000004b220c AdmVolDelThread
ANR9999D Thread<22998> 0x00000000c01af4 StartThread
ANR9999D Thread<22998> 0x000039ba00677d *UNKNOWN*
ANR9999D Thread<22998> 0x000039b94d325d *UNKNOWN*
ANR1181E dftxn.c(212): Data storage transaction 0:3.186769174 was aborted.

Any ideas?

=

Not sure if you mean the actual external storage is really gone?

If the volume is still physically accessible, run audit volume /TSM_POOL/19/data19 fix=yes.

If you haven't done so already, do: restore volume /TSM_POOL/19/data19 preview=yes
Look in the activity log to see if it gives you volume names from your copy pool, so you can recreate the data (on other volumes in TSM_POOL ) from your copy pool tapes. If you can, the volume will go empty and you can delete it without the discardd=yes.

If the storage is really physically gone, I think you could resort to creating a fake /TSM_POOL/19/data19 on another physical volume, then run audit volume /TSM_POOL/19/data19 fix=yes.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of Davis, Jim J - (jjdavis)
Sent: Wednesday, April 11, 2012 4:26 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] delete volume failure under TSM 5.5.6

This is on a RHEL 5.7 x86_64 system; an old stgpool volume on external storage failed, so I marked it "destroyed", and then tried to run

del vol /the/volume/name discarddata=yes

That fails with

ANR2017I Administrator ADMIN issued command: DELETE VOLUME /TSM_POOL/19/data19 discarddata=yes ANR0984I Process 1836 for DELETE VOLUME (DISCARD DATA) started in the BACKGROUND at 01:19:56 PM.
ANR2222I Discard Data process started for volume /TSM_POOL/19/data19 (process ID 1836).
ANR9999D_2990890315 PrepareClusters(dftxn.c:875) Thread<22998>: Logical occupancy went negative for Pool 25, Ck1=75, Ck2=1.
ANR9999D Thread<22998> issued message 9999 from:
ANR9999D Thread<22998> 0x00000000b95ba2 OutDiagToCons ANR9999D Thread<22998> 0x00000000b986a9 outDiagfExt ANR9999D Thread<22998> 0x00000000610e01 DfPrepareTxn ANR9999D Thread<22998> 0x000000005e05a1 bfPrepareTxn ANR9999D Thread<22998> 0x00000000b682c1 CollectVotes ANR9999D Thread<22998> 0x00000000b686b4 tmEnd ANR9999D Thread<22998> 0x000000004b220c AdmVolDelThread ANR9999D Thread<22998> 0x00000000c01af4 StartThread ANR9999D Thread<22998> 0x000039ba00677d *UNKNOWN* ANR9999D Thread<22998> 0x000039b94d325d *UNKNOWN* ANR1181E dftxn.c(212): Data storage transaction 0:3.186769174 was aborted.

Any ideas?

Try to audit volume with fix=yes, if it is still presented

Grigori G. Solonovitch
Senior Technical Architect Ahli United Bank Kuwait www.ahliunited.com.kw

Please consider the environment before printing this E-mail


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of Davis, Jim J - (jjdavis)
Sent: 11 04 2012 11:26 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] delete volume failure under TSM 5.5.6

This is on a RHEL 5.7 x86_64 system; an old stgpool volume on external storage failed, so I marked it "destroyed", and then tried to run

del vol /the/volume/name discarddata=yes

That fails with

ANR2017I Administrator ADMIN issued command: DELETE VOLUME /TSM_POOL/19/data19 discarddata=yes ANR0984I Process 1836 for DELETE VOLUME (DISCARD DATA) started in the BACKGROUND at 01:19:56 PM.
ANR2222I Discard Data process started for volume /TSM_POOL/19/data19 (process ID 1836).
ANR9999D_2990890315 PrepareClusters(dftxn.c:875) Thread<22998>: Logical occupancy went negative for Pool 25, Ck1=75, Ck2=1.
ANR9999D Thread<22998> issued message 9999 from:
ANR9999D Thread<22998> 0x00000000b95ba2 OutDiagToCons ANR9999D Thread<22998> 0x00000000b986a9 outDiagfExt ANR9999D Thread<22998> 0x00000000610e01 DfPrepareTxn ANR9999D Thread<22998> 0x000000005e05a1 bfPrepareTxn ANR9999D Thread<22998> 0x00000000b682c1 CollectVotes ANR9999D Thread<22998> 0x00000000b686b4 tmEnd ANR9999D Thread<22998> 0x000000004b220c AdmVolDelThread ANR9999D Thread<22998> 0x00000000c01af4 StartThread ANR9999D Thread<22998> 0x000039ba00677d *UNKNOWN* ANR9999D Thread<22998> 0x000039b94d325d *UNKNOWN* ANR1181E dftxn.c(212): Data storage transaction 0:3.186769174 was aborted.

Any ideas?



Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.

Call TSM support and have them help you fix your TSM DB.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of Davis, Jim J - (jjdavis)
Sent: Wednesday, April 11, 2012 4:26 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] delete volume failure under TSM 5.5.6

This is on a RHEL 5.7 x86_64 system; an old stgpool volume on external storage failed, so I marked it "destroyed", and then tried to run

del vol /the/volume/name discarddata=yes

That fails with

ANR2017I Administrator ADMIN issued command: DELETE VOLUME /TSM_POOL/19/data19
discarddata=yes
ANR0984I Process 1836 for DELETE VOLUME (DISCARD DATA) started in the
BACKGROUND at 01:19:56 PM.
ANR2222I Discard Data process started for volume /TSM_POOL/19/data19 (process
ID 1836).
ANR9999D_2990890315 PrepareClusters(dftxn.c:875) Thread<22998>: Logical
occupancy went negative for Pool 25, Ck1=75, Ck2=1.
ANR9999D Thread<22998> issued message 9999 from:
ANR9999D Thread<22998> 0x00000000b95ba2 OutDiagToCons
ANR9999D Thread<22998> 0x00000000b986a9 outDiagfExt
ANR9999D Thread<22998> 0x00000000610e01 DfPrepareTxn
ANR9999D Thread<22998> 0x000000005e05a1 bfPrepareTxn
ANR9999D Thread<22998> 0x00000000b682c1 CollectVotes
ANR9999D Thread<22998> 0x00000000b686b4 tmEnd
ANR9999D Thread<22998> 0x000000004b220c AdmVolDelThread
ANR9999D Thread<22998> 0x00000000c01af4 StartThread
ANR9999D Thread<22998> 0x000039ba00677d *UNKNOWN*
ANR9999D Thread<22998> 0x000039b94d325d *UNKNOWN*
ANR1181E dftxn.c(212): Data storage transaction 0:3.186769174 was aborted.

Any ideas?

Hi,

be4 going into the support call one can try and do an "audit vol xxx fix=yes" to see if that clears things.

Kind regards,

Karel




----- Oorspronkelijk bericht -----
Van: Ehresman,David E. <deehre01 < at > LOUISVILLE.EDU>
Verzonden: donderdag 12 april 2012 16:10
Aan: ADSM-L < at > VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] delete volume failure under TSM 5.5.6

Call TSM support and have them help you fix your TSM DB.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of Davis, Jim J - (jjdavis)
Sent: Wednesday, April 11, 2012 4:26 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] delete volume failure under TSM 5.5.6

This is on a RHEL 5.7 x86_64 system; an old stgpool volume on external storage failed, so I marked it "destroyed", and then tried to run

del vol /the/volume/name discarddata=yes

That fails with

ANR2017I Administrator ADMIN issued command: DELETE VOLUME /TSM_POOL/19/data19
discarddata=yes
ANR0984I Process 1836 for DELETE VOLUME (DISCARD DATA) started in the
BACKGROUND at 01:19:56 PM.
ANR2222I Discard Data process started for volume /TSM_POOL/19/data19 (process
ID 1836).
ANR9999D_2990890315 PrepareClusters(dftxn.c:875) Thread<22998>: Logical
occupancy went negative for Pool 25, Ck1=75, Ck2=1.
ANR9999D Thread<22998> issued message 9999 from:
ANR9999D Thread<22998> 0x00000000b95ba2 OutDiagToCons
ANR9999D Thread<22998> 0x00000000b986a9 outDiagfExt
ANR9999D Thread<22998> 0x00000000610e01 DfPrepareTxn
ANR9999D Thread<22998> 0x000000005e05a1 bfPrepareTxn
ANR9999D Thread<22998> 0x00000000b682c1 CollectVotes
ANR9999D Thread<22998> 0x00000000b686b4 tmEnd
ANR9999D Thread<22998> 0x000000004b220c AdmVolDelThread
ANR9999D Thread<22998> 0x00000000c01af4 StartThread
ANR9999D Thread<22998> 0x000039ba00677d *UNKNOWN*
ANR9999D Thread<22998> 0x000039b94d325d *UNKNOWN*
ANR1181E dftxn.c(212): Data storage transaction 0:3.186769174 was aborted.

Any ideas?