Welcome! » Log In » Create A New Profile

container with damaged extents

Posted by J. Eric Wonderley 
J. Eric Wonderley
container with damaged extents
January 31, 2019 05:59AM
Looking thru my actlog I noticed msgs like these:
01/30/2019 08:59:07 ANR4847W REPLICATE NODE detected an extent with ID
9421329176063255953 on container
/orion_c3/18/0000000000001843.ncf that is marked
damaged. (SESSION: 65110496, PROCESS: 31257)
01/30/2019 08:59:08 ANR4847W REPLICATE NODE detected an extent with ID
391953834519091250 on container
/orion_c2/11/000000000000112d.ncf that is marked
damaged. (SESSION: 65110496, PROCESS: 31257)
01/30/2019 08:59:08 ANR4847W REPLICATE NODE detected an extent with ID
9421329176063255953 on container
/orion_c3/18/0000000000001843.ncf that is marked

Also this:
Protect: YACHT>q damaged orioncontain

Storage Pool Name Non-Deduplicated Extent Deduplicated
Extent Cloud Orphaned Extent
Count Count
Count
------------------------- ---------------------------
----------------------- -----------------------
ORIONCONTAIN 31 0

What is typically done to resolve this? I do replication and my target
doesn't show any damaged extents.
This message was imported via the External PhorumMail Module
Loon, Eric van (ITOP NS) - KLM
Re: container with damaged extents
January 31, 2019 05:59AM
Hi Eric!
Checkout the repair stgpool command at https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.6/srv.reference/r_cmd_stgpool_repair.html
Kind regards,
Eric van Loon
Air France/KLM Storage & Backup


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of J. Eric Wonderley
Sent: donderdag 31 januari 2019 14:17
To: ADSM-L@VM.MARIST.EDU
Subject: container with damaged extents

Looking thru my actlog I noticed msgs like these:
01/30/2019 08:59:07 ANR4847W REPLICATE NODE detected an extent with ID
9421329176063255953 on container
/orion_c3/18/0000000000001843.ncf that is marked damaged. (SESSION: 65110496, PROCESS: 31257)
01/30/2019 08:59:08 ANR4847W REPLICATE NODE detected an extent with ID
391953834519091250 on container
/orion_c2/11/000000000000112d.ncf that is marked damaged. (SESSION: 65110496, PROCESS: 31257)
01/30/2019 08:59:08 ANR4847W REPLICATE NODE detected an extent with ID
9421329176063255953 on container
/orion_c3/18/0000000000001843.ncf that is marked

Also this:
Protect: YACHT>q damaged orioncontain

Storage Pool Name Non-Deduplicated Extent Deduplicated
Extent Cloud Orphaned Extent
Count Count
Count
------------------------- ---------------------------
----------------------- -----------------------
ORIONCONTAIN 31 0

What is typically done to resolve this? I do replication and my target doesn't show any damaged extents.
********************************************************
For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
********************************************************
This message was imported via the External PhorumMail Module
PAC Brion Arnaud
Re: container with damaged extents
January 31, 2019 05:59AM
Hi J. Eric,

The normal recovery path is to make use of "repair stgpool" command, which should be fixing the damaged container, making use of the data that has already been replicated to your destination server.

You might then perform an audit from the involved containers (audit container /orion_c3/18/0000000000001843.ncf) to confirm everything is fine, and in the case where some extents would still be damaged, have to remove them, making use of the "action=removedamaged" option available in "audit container" command.

Cheers.

Arnaud

********************************************************************************************************************************
Backup and Recovery Systems Administrator
Panalpina Management Ltd., Basle, Switzerland,
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion@panalpina.com
This electronic message transmission contains information from Panalpina and is confidential or privileged.
This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this
information is strictly prohibited.

If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you.
********************************************************************************************************************************
www.panalpina.com



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of J. Eric Wonderley
Sent: Thursday, January 31, 2019 2:17 PM
To: ADSM-L@VM.MARIST.EDU
Subject: container with damaged extents

Looking thru my actlog I noticed msgs like these:
01/30/2019 08:59:07 ANR4847W REPLICATE NODE detected an extent with ID
9421329176063255953 on container
/orion_c3/18/0000000000001843.ncf that is marked
damaged. (SESSION: 65110496, PROCESS: 31257)
01/30/2019 08:59:08 ANR4847W REPLICATE NODE detected an extent with ID
391953834519091250 on container
/orion_c2/11/000000000000112d.ncf that is marked
damaged. (SESSION: 65110496, PROCESS: 31257)
01/30/2019 08:59:08 ANR4847W REPLICATE NODE detected an extent with ID
9421329176063255953 on container
/orion_c3/18/0000000000001843.ncf that is marked

Also this:
Protect: YACHT>q damaged orioncontain

Storage Pool Name Non-Deduplicated Extent Deduplicated
Extent Cloud Orphaned Extent
Count Count
Count
------------------------- ---------------------------
----------------------- -----------------------
ORIONCONTAIN 31 0

What is typically done to resolve this? I do replication and my target
doesn't show any damaged extents.
This message was imported via the External PhorumMail Module
Sorry, only registered users may post in this forum.

Click here to login