Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1557758.1
Update Date:2016-02-09
Keywords:
Solution Type  Problem Resolution Sure

Solution  1557758.1 :   Sun Storage 7000 Unified Storage System: Cannot destroy 'old' replication actions  

Related Items 
    

  • Sun ZFS Storage 7320
    •  
  • Sun Storage 7210 Unified Storage System
    •  
  • Oracle ZFS Storage ZS3-BA
    •  
  • Oracle ZFS Storage Appliance Racked System ZS4-4
    •  
  • Oracle ZFS Storage ZS3-2
    •  
  • Sun Storage 7410 Unified Storage System
    •  
  • Oracle ZFS Storage ZS3-4
    •  
  • Sun ZFS Storage 7420
    •  
  • Sun Storage 7310 Unified Storage System
    •  
  • Oracle ZFS Storage ZS4-4
    •  
  • Sun Storage 7110 Unified Storage System
    •  
  • Sun ZFS Storage 7120
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
    •  






In this Document


Symptoms


Cause


Solution


References

Created from <SR 3-7133828021>


Applies to:  

Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7110 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7210 Unified Storage System - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)



Symptoms


To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Disk Storage ZFS Storage Appliance


Cannot destroy old replication actions:

On Source we have:


NAShead1:shares mbox50 replication> show
Actions: 
  
  TARGET STATUS NEXT 
action-000 NAShead1 cancelling disabled 
action-001 NAShead1 cancelling disabled 
  

NAShead1:shares mbox50 replication> destroy action-000 
This will destroy "action-000". Are you sure? (Y/N) 
  

NAShead1:shares mbox50 replication> show
Actions: 
  
  TARGET STATUS NEXT 
action-000 NAShead1 cancelling disabled 
action-001 NAShead1 cancelling disabled


 


Cause


Replication actions remain in "cancelling" state and they can't be destroyed.

This is preventing the customer carrying out new replication setup/configuration activities.



I see several issues here that effect akd and possibly akd's ability to carry out requested Replication cancelling actions ...



I see excessive Log files listed in the Bundle for Node NAShead1


ak.NAShead1-SN-toro-2013-04-15.06.14.25/logs $ ls -ltr | wc -l
  817



800+ log files here....



cores2-da-x64-4:ak.NAShead1-SN-toro-2013-04-15.06.14.25/logs $ du -hs .
  81M .


Please follow the MOS document below to remove these:

1408493.1 - Sun Storage 7000 Unified Storage System: BUI/CLI hang due to 'excessive' amount of 'old' log files




There are also excessive Analytics present as well:


ak.NAShead1-SN-toro-2013-04-15.06.14.25/status $ more datasets.out
Datasets:

In particular these large ones...These need deleting..clearing.

DATASET STATE INCORE ONDISK NAME
dataset-000 active 4.01M 7.10G arc.accesses[hit/miss]
dataset-001 active 1.29M 3.01G arc.l2_accesses[hit/miss]
dataset-004 active 2.30M 4.64G arc.size[component]
dataset-006 active 1.05M 2.82G cpu.utilization[mode]
dataset-007 active 1.29M 3.05G dnlc.accesses[hit/miss]
dataset-013 active 1.29M 3.03G io.bytes[op]
dataset-014 active 517K 1.57G io.disks[utilization=95][disk]
dataset-016 active 37.7M 52.5G io.ops[disk]
dataset-017 active 1.29M 3.03G io.ops[op]
dataset-027 active 9.83M 15.4G nfs4.ops[op]
dataset-029 active 1.84M 3.28G nic.kilobytes[device]
dataset-030 active 1.29M 3.03G nic.kilobytes[direction]
dataset-034 active 1.02M 3.02G tcp.bytes[local service]


Please see the following document for resolution:


1401595.1 - Sun Storage 7000 Unified Storage System: BUI/CLI hang due to 'excessive' analytics collected



After these actions have been completed on both Nodes, please then check cancelling Replication actions again.


We might need to issue the destroy commands again on those Actions.
 


Solution


After customer removed old logfiles and excessive Analytics data from there array, old replication actions were confirmed as successfully cancelled by the Appliance Software AKD.

1401595.1 - Sun Storage 7000 Unified Storage System: BUI/CLI hang due to 'excessive' analytics collected

1408493.1 - Sun Storage 7000 Unified Storage System: BUI/CLI hang due to 'excessive' amount of 'old' log files


 


PLEASE NOTE:  Tidying up the AKD analytics/logs may assist in proving a 'clean' environment for AKD, but the actual restart of AKD may have provided the definitive resolution to this issue.


References
<NOTE:1401595.1> - Sun Storage 7000 Unified Storage System: BUI/CLI hang due to 'excessive' analytics collected
<NOTE:1508081.1> - Sun ZFS Storage Appliance: Project Replication is failing while doing Active Head failover 
<NOTE:1408493.1> - Sun Storage 7000 Unified Storage System: BUI/CLI hang due to 'excessive' amount of 'old' log files



Attachments

This solution has no attachment


















       

Copyright © 2018 Oracle, Inc.  All rights reserved.

 Feedback