![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||
Solution Type Sun Alert Sure Solution 2132072.1 : On FS1-2 Systems, Migration of Large Volume Extents May Lead to Controller Panics and Data Loss
In this Document
Applies to:Oracle FS1-2 Flash Storage SystemSun Software - Generic Sun Hardware - Generic Information in this document applies to any platform. ________________________________________ Bug 23110513 Date of Resolved Release: 28-Apr-2016 ________________________________________ DescriptionAn Extent is a contiguous space in a Drive Group associated with a single Volume. There is an Extent size limitation of 2 Terabytes on the amount of data that can be moved during a data migration or rebalancing in a QoS (Quality of Service) migration. Migration of Extents beyond this limitation will panic the controller, causing the data beyond 2 Terabytes to be lost. If several panics occur, the FS1-2 may also shutdown. OccurrenceThis issue can occur on any Flash Storage System FS1-2 that meets all of the following conditions: 1. System is running software version 06.02.03-0280.01 or earlier. 2. Single Tiered LUNs larger than 2 Terabytes. 3. Free space of 2 Terabytes or more in the Storage Domain and Storage Class. 4. Data migration is triggered by any of the following:
SymptomsWhen encountered, this issue will panic the controller executing the migration. This will generate a log bundle with the following event: VOLUMES_HAVE_CHANGED_STATE_COLLECT_LOGS There will also be the following entry in the Event Log: Volumes have changed state in a bad way with a description of: One or more volumes have changed state in a bad way. This event is to tell us to collect logs as a result of the changes that took place. WorkaroundThe immediate workaround for this issue is to disable Automatic QoS Rebalancing for the Storage Domain(s) and to avoid adding or subtracting Drive Groups to or from a Storage Domain. For information on how to disable Automatic QoS Rebalancing, please reference the following document:
Customers who meet all of the remaining conditions described above should open a Service Request to have Oracle Support verify their exposure. A current log bundle will be needed. Please reference the following document for additional information:
For customers that cannot provide a log bundle, Oracle has added a utility, codAudit, to the "2of2" in patch 23132401 (Release 6.2.3-0280.02). It can be used to identify 'Single Tiered' LUNs with Extents larger than 2TB. Customers should contact Oracle support for assistance in running this utility as well as its interpretation. Resolution This issue is addressed in the following release:
Patches<Patch 23132401> History28-Apr-2016: Document released, status Resolved Internal Section: Comments: Controller Panic string: 2016-04-15T01:32:10.116926695Z 74191176 508002000158C1A1 11 0 546 EMERG STRACESTR /home/build/builds/axiom/060203-028000/src/slammer/bs/cfg/bs_cfg_shared.c 4424 bs_cfgSharedCmdPreTimeout BS BS "PANIC: cmdSlot:0x0 cmdCode:0x35 cmdStep" Details on the utility to identify this issue are detailed in Document 2129692.1 Questions regarding this document should be addressed to Internal Contributor/Submitter: bob.deguc@oracle.com References<NOTE:2045089.1> - FS System: How to Enable or Disable Automatic QoS (Quality of Service) Rebalancing<NOTE:1943289.1> - FS System: How to Attach a Manual Log Bundle to an Existing MOS Service Request <BUG:23110513> - CONTROLLER-02 FAILED AND MANY DGS FAILED Attachments This solution has no attachment |
||||||||||||||||||||||||
|