Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Sun Alert Sure Solution 1001296.1 : 5210/5220/5310/5320 NAS Systems May Panic When "checkpoint" is Enabled
PreviouslyPublishedAs 201756 Product Sun StorageTek 5310 NAS Appliance Sun StorageTek 5320 NAS Appliance Sun StorageTek 5210 NAS Appliance Bug Id <SUNBUG: 6477728> Date of Resolved Release 06-DEC-2006 Impact This issue causes a system panic. Contributing Factors This issue can occur on the following releases:
Note: this issue is with release 4.20 M0 and 4.20 M1 of the NAS OS. The NAS OS version can be found on the main panel of the Web Admin or by issuing the 'version' command from the console. Symptoms The panic stack trace is similar to the following: STACK TRACE: 0xD52E58 dbg_int3+0x1(294D28 2CE186 2CE173 4FD) 0xD52E78 assert_botch+0x22(2CE186 2CE173 4FD 1E3C20) 0xD52EE8 sfs2sa_commit+0x945(D52F60 7 D52F98 1DF066) 0xD52EF8 sfs2xa_commit+0x4C(0 57D5000 0 1DEEEF) 0xD52F98 sfs2cp_del_chkpnt+0xC2(57D5000 0 D52FD4 D52FCC) 0xD52FD8 sfs2cp_cleaner+0xFA(57D5000 206 1CA814 0) 0xD52FF8 thread_launcher+0x28(D43000 0 114CEA D5AF5C)
Workaround There is no workaround for this issue. Do not disable checkpoints, which are enabled by default, due to CR 6505434. See Page 170 of the Sun StorageTek NAS OS Administration Guide (819-4284-10)"Managing File System Checkpoints" available at: http://docs.sun.com/app/docs/doc/819-4284-10 Resolution This issue is addressed in the following releases:
Modification History Date: 22-JAN-2007
References<SUNPATCH: 118216-11><SUNPATCH: 119351-09> <SUNPATCH: 119352-04> <SUNPATCH: 119353-01> Previously Published As 102743 Internal Comments The problem is happening when a checkpoint in an almost full and fragmented file system is being deleted. The fix is to make sure that the number of pages in transaction limit is not exceeded. PLEASE NOTE: Other issues are also resolved by upgrading per above:
Please stress the importance of these fixes with your customers and encourage them to upgrade. Internal Contributor/submitter [email protected] Internal Eng Business Unit Group NWS (Network Storage) Internal Eng Responsible Engineer [email protected], [email protected], [email protected] Internal Services Knowledge Engineer [email protected] Internal Escalation ID 1-19738655 Internal Resolution Patches 118216-11, 119351-09, 119352-04, 119353-01 Internal Sun Alert Kasp Legacy ID 102743 Internal Sun Alert & FAB Admin Info Critical Category: Availability ==> Severe Significant Change Date: 2006-12-06 Avoidance: Patch Responsible Manager: Gregory Matthews Original Admin Info: [WF 05-Dec-2006, karened: all pending patches on sunsolve per olafs automation. updated SA and will release today - went to sunalert_review yesterday] [WF 04-Dec-2006, karened: created from very incomplete submittal as a FAB but meets SA criteria. I still need confirmation on Pending Patches] Internal SA-FAB Eng Submission -------- Original Message -------- Subject: Draft Field Action Bulletin /Synopsis: 5xxx NAS Appliance could panic during checkpoint deletion. Date: Thu, 30 Nov 2006 18:24:34 -0700 From: Clifford Thomas Reply-To: [email protected] To: Henry Davis Jr --------------------------------------------------------------- Synopsis: 5xxx NAS Appliance could panic during checkpoint deletion. Avoidance: [ ] Binary [ ] T-Patch [ ] Patch [ ] Firmware [ ] Hardware [X] Upgrade [X] Workaround [ ] Reconfiguration [ ] Service Procedure [ ] None [ ] Hardware Replacement (Must follow SMI FCO Process) * * Note:Please follow the below link for details on how to submit an FCO; http://sunwebcollab.central.sun.com/gm/folder-1.11.811470 Implementation: [ ] Reactive (Upon Failure) [x ] Controlled Proactive (H/W FABs require Customer List and Customer Letter) [ ] Mandatory (Requires Customer List and Customer Letter) Product: StorEdge 5210 NAS StorEdge 5310 NAS XTA5320R StorageTek 5320 NAS Affected X-Options: N/A Affected Parts: N/A Issue Description: Impact This issue causes a system panic. Contributing Factors Checkpoints must be enabled. Symptoms System panic. Root Cause The problem is happening when a checkpoint in an almost full and fragmented file system is being deleted. This problem is not easy to reproduce. The fix is to make sure that the number of pages in transaction limit is not exceeded. The issue was resolved with a maintenance release of the NAS OS. (4.20 M2) Corrective Action: Supported Workaround (if available) Disable checkpointing on all volumes. Final Resolution Upgrade NAS OS to release 4.20 M2 Sun StorageTek NAS OS Administration Guide (819-4284-10) Page 185: Upgrading NAS Software Identification of Affected Parts (how to): This issue is found in release 4.20 M0 and 4.20 M1 of the NAS OS. The NAS OS version can be found on the main panel of the Web Admin or by issuing the 'version' command from the console. Hardware Remediation and Material Availability Details: (For Hardware FABs only) N/A Comments: N/A References: * BugID: 6477728 * Escalation ID: 1-19738655 * Sun Alert: * Pending Patches: * Resolution Patches: * Other References: * Reference Manual: * Related URL(s): * ECO: * GSAP: * WW Stop Ship: * Radiance ID: Contacts: * Contributor: * Responsible Engineer: Faramarz Jalalian * Responsible Manager: Gregory Matthews * Business Unit Group: [ ] SSG WGS (Workgroup Systems) [ ] SSG NSN (Netra Systems and Networking) [ ] SSG ES (Enterprise Systems) [ ] SSG SW (Platform Software) [ ] SSG PNP (Processor) [ ] NSG (Network Systems Group) [X] NWS (Network Storage) [ ] OP/N1 RPE (Operating Platforms/N1 Revenue Product Engin.) [ ] JPSE (Java Platform Sustaining Engineering) [ ] JWSSE (Java Web Services Sustaining Engineering) [ ] USG (User Software Group) [ ] Other - Please specify -- Cliff Thomas Sun Microsystems Inc 303-395-3378 Product_uuid 63654ce5-f88d-11d8-ab63-080020a9ed93|Sun StorageTek 5310 NAS Appliance 7656ca7b-9cd4-11da-85b4-080020a9ed93|Sun StorageTek 5320 NAS Appliance d4e4fc3d-7c3f-11d8-9e3a-080020a9ed93|Sun StorageTek 5210 NAS Appliance ReferencesSUNPATCH:118216-11SUNPATCH:119351-09 SUNPATCH:119352-04 SUNPATCH:119353-01 Attachments This solution has no attachment |
||||||||||||
|