Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2008.1050 -- [Solaris]
ZFS Pool Corruption May Occur With Sun Cluster 3.2 Running
Solaris 10 with patch 137137-09 or 137138-09
14 November 2008
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Solaris 10 Operating System
OpenSolaris
Publisher: Sun Microsystems
Operating System: Solaris
Impact: Denial of Service
Access: Existing Account
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-245626-1
- --------------------------BEGIN INCLUDED TEXT--------------------
Solution Type: Sun Alert
Solution 245626 : ZFS Pool Corruption May Occur With Sun Cluster
3.2 Running Solaris 10 with patch 137137-09 or 137138-09
Bug ID: 6769612
Product
Solaris 10 Operating System
OpenSolaris
Date of Workaround Release: 12-Nov-2008
SA Document Body
ZFS Pool Corruption May Occur With Sun Cluster 3.2 Running Solaris 10
with patch 137137-09 or 137138-09
1. Impact
A change to the zpool_import() management of the zpool.cache file as
delivered by kernel patches 137137-09 (for SPARC) or 137138-09
(for x86) may cause systems that have their shared ZFS (zfs(1M)) pools
under the control of Sun Cluster's HAStoragePlus to be simultaneously
imported on multiple cluster nodes.
Importing a ZFS pool on multiple cluster nodes will result in pool
corruption which may cause data integrity issues or cause a cluster
node to panic.
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform:
* Sun Cluster 3.2 on Solaris 10 with patch 137137-09
* Open High Availability Cluster on OpenSolaris based upon builds
snv_77 through snv_103
x86 Platform:
* Sun Cluster 3.2 on Solaris 10 with patch 137138-09
* Open High Availability Cluster on OpenSolaris based upon builds
snv_77 through snv_103
Notes:
1. Solaris 8 and 9 are not impacted by this issue.
2. Sun Cluster 3.0 and 3.1 are not impacted by this issue. Although
Sun Cluster 3.1 runs on Solaris 10, HAStoragePlus does not suport
ZFS.
3. Systems are only vulnerable to this issue if they use Sun Cluster's
HAStoragePlus to manage their ZFS pools (see zpool(1M)).
4. This issue does not occur during normal operation. Systems are only
impacted by this issue if an event occurs which causes the automated
import of a ZFS pool to a second cluster node to occur. This automated
import of ZFS pools may occur when a cluster node reboots due to a
system panic, power loss, maintenance, or failover occurring. Then
(under certain circumstances), this issue may occur. Other scenarios
may also cause this issue.
3. Symptoms
A situation where a ZFS pool has been imported on more than one node
can be identified by running the following command on all Cluster
nodes and checking if a zpool(1M) has been imported on multiple nodes
simultaneously:
# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
pool1 49.7G 528K 49.7G 0% ONLINE -
pool2 54.7G 486K 54.7G 0% ONLINE -
Check the same pool NAME is not seen on multiple cluster nodes.
Once a ZFS pool has been simultaneously imported on multiple cluster
nodes, then system panics and zpool import hangs may occur. This list
is not exhaustive and other symptoms might be seen.
In addition, a system which is vulnerable to this issue may see the
following warning:
Reading ZFS config: *WARNING: pool 'test1' could not be loaded as it
was last accessed by another system
(host: pbeer2 hostid: 0x8360f76b). See:
http://www.sun.com/msg/ZFS-8000-EY done.
This warning does not mean that the system has got a ZFS pool
simultaneously imported on multiple cluster nodes. It only means that
the system configuration defined in the contributing factors (see
section 2 above) has been met. A trigger event is still required to
be susceptible to this issue.
4. Workaround
Binary relief is available through normal support channels.
Note that relief should be installed immediately after the kernel
patches 137137-09/137138-09 and before the system is rebooted
to reduce the chance for this issue to occur.
Alternatively, the affected patches should be removed before any ZFS
pools are simultaneously imported to two cluster nodes.
Note that systems with Solaris 10 10/08 or later installed cannot back
out the affected patches, as these patches are preinstalled. There is
no back out package available for patchrm(1M) to use.
5. Resolution
This issue is addressed in the following releases:
SPARC Platform:
* OpenSolaris based upon builds snv_104 or later
x86 Platform:
* OpenSolaris based upon builds snv_104 or later
A final resolution is pending completion for Solaris 10.
This Sun Alert notification is being provided to you on an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT
YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE
OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN.
This Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements.
Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQCVAwUBSRzaxSh9+71yA2DNAQJm2AQAj/+JICmq0QdplC7Y7hdTImUvWIZZGviq
/bAOaq62vyFz2z0jtYnmIpL40RYArScVMvkLhNVfL0MKaHOtBtORlr/sr++Dcpi+
OQk9Bv/wDcy1eQtixXlzB0zLvh1c5vSIiz8cZihV0nZ4pbTmaYVcQZ5l1GICFO9s
jD3pE9W8XM4=
=5Riv
-----END PGP SIGNATURE-----