- 论坛徽章:
- 0
|
i got it
Document Audience: PUBLIC
Document ID: 101562
Old Document ID: (formerly 57636)
Title: VxVM Encapsulated Disk With UFS Logging Enabled May Result in Persistent Warning Messages, System Panic or Failure to Boot
Copyright Notice: Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date: Thu Dec 15 00:00:00 MST 2005
--------------------------------------------------------------------------------
Status Issued
Description Top
Sun(sm) Alert Notification
Sun Alert ID: 101562 (formerly 57636)
Synopsis: VxVM Encapsulated Disk With UFS Logging Enabled May Result in Persistent Warning Messages, System Panic or Failure to Boot
Category: Availability
Product: VERITAS Volume Manager 3.5 Software, VERITAS Volume Manager 4.0 Software
BugIDs: 5045578
Avoidance: Patch, Workaround
State: Resolved
Date Released: 22-Sep-2004, 05-Dec-2005
Date Closed: 05-Dec-2005
Date Modified: 03-May-2005, 08-Apr-2005, 15-Mar-2005, 03-Feb-2005, 11-Jan-2005, 30-Jun-2005, 07-Sep-2005, 05-Dec-2005, 15-Dec-2005
1. Impact
"Root" disk encapsulated with VERITAS Volume Manager (VxVM) 3.5, 4.0 or 4.1 and with ufs logging enabled may result in persistent warning messages, and in some cases the system may panic or fail to boot.
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
VERITAS Volume Manager (VxVM) 3.5 (for Solaris 9) without 3.5MP4 maintenance patch 112392-08
VERITAS Volume Manager (VxVM) 4.0 (for Solaris 9) without 4.0MP2 maintenance patch 115217-05
VERITAS Volume Manager (VxVM) 4.1 (for Solaris 9 or 10) without 4.1MP1 maintenance patch 117080-04
Notes:
Solaris 7 and Solaris 8 are not affected by this issue. Solaris on the x86 Platform is not affected by this issue.
Logging is enabled by default on Solaris 9 (Update 7) or with patch 113073-09 and above.
This issue only occurs when both "root disk" is encapsulated and logging is enabled.
Logging is turned off by default in VERITAS Volume Manager (VxVM) 4.1 for Solaris 10
This issue can occur when the lower layers return errors on writes that logging is executing while trying to mount the "root" filesystem. Logging is trying to roll the log or update its "state" information on disk, but writes to an encapsulated root disk this early in the boot process is not allowed. (Note that this issue does not occur when the "root disk" is un-encapsulated). The writes fail, warning messages are generated, and if the mount of the root filesystem fails, the system will panic and fail to boot.
3. Symptoms
Should this issue occur, messages on the console during bootup will appear similar to the following:
WARNING: Error writing ufs log state
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run fsck(1M)
WARNING: Error writing master during ufs log roll
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run fsck(1M)
Cannot mount root on /pseudo/vxio@0:0 fstype ufs
panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root
Solution Summary Top
4. Relief/Workaround
To work around the described issue, edit the "/etc/vfstab" file (and any other boot volumes that are created by VERITAS Volume Manager, for example, "/", "/usr", "/var", "/opt") and add "nologging" to the mount option of those volumes, as in the following example:
/dev/vx/dsk/bootdg/rootvol /dev/vx/rdsk/bootdg/rootvol / ufs 1 no nologging
/dev/vx/dsk/bootdg/usr /dev/vx/rdsk/bootdg/usr /usr ufs 1 no nologging
/dev/vx/dsk/bootdg/var /dev/vx/rdsk/bootdg/var /var ufs 1 no nologging
/dev/vx/dsk/bootdg/opt /dev/vx/rdsk/bootdg/opt /opt ufs 2 yes nologging
and then reboot the system.
If a system panic occurs, boot the system from either a Solaris CD or from the network and remount the affected volumes, as in the following example:
ok> boot net -s
# mount /dev/dsk/c0t0d0s0 /mnt
# sync
# umount /mnt
# mount /dev/dsk/c0t1d0s0 /mnt
# sync
and then reboot the system twice.
Notes:
The reason to reboot twice is that the first time you mount with nologging, it has to deallocate the log first, and thus is still mounted with "logging" enabled. After the second time, the system is really mounted with "nologging" enabled.
In a Sun Cluster environment, "/globaldevices" does not require "nologging".
To change the nologging setting if it was defined earlier, edit the "/etc/vfstab" file (and any other boot volumes that are created by VERITAS Volume Manager, for example, "/", "/usr", "/var", "/opt") and remove "nologging" to the mount option of those volumes, as in the following example:
/dev/vx/dsk/bootdg/rootvol /dev/vx/rdsk/bootdg/rootvol / ufs 1 no -
/dev/vx/dsk/bootdg/usr /dev/vx/rdsk/bootdg/usr /usr ufs 1 no -
/dev/vx/dsk/bootdg/var /dev/vx/rdsk/bootdg/var /var ufs 1 no -
/dev/vx/dsk/bootdg/opt /dev/vx/rdsk/bootdg/opt /opt ufs 2 yes -
Once you have changed the nologging setting, reboot the system.
5. Resolution
SPARC Platform
VERITAS Volume Manager (VxVM) 3.5 (for Solaris 9) with 3.5MP4 maintenance patch 112392-08 or later
VERITAS Volume Manager (VxVM) 4.0 (for Solaris 9) with 4.0MP2 maintenance patch 115217-05 or later
VERITAS Volume Manager (VxVM) 4.1 (for Solaris 9 or 10) with 4.1MP1 maintenance patch 117080-04 or later
To verify if logging is enabled, "logging" should be shown from the output of "mount -v", as in the following example:
# mount -v
/dev/vx/dsk/rootvol on / type ufs
read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=4ec0000
on Thu Apr 28 16:06:52 2005
Note: You can also explicitly add logging to the "/etc/vfstab" file.
These patch releases support UFS logging on a VxVM encapsulated root disk. If you have previously disabled UFS logging (by setting the "nologging" option in /etc/vfstab), you may now restore UFS logging after installing this release.
To change the nologging setting, edit the "/etc/vfstab" file (and any other boot volumes that are created by VERITAS Volume Manager, for example, "/", "/usr", "/var", "/opt") and remove "nologging" from the mount option of those volumes, as in the following example:
/dev/vx/dsk/bootdg/rootvol /dev/vx/rdsk/bootdg/rootvol / ufs 1 no -
After you have changed the nologging setting, reboot the system.
To verify if logging is enabled, "logging" should be shown from the output of "mount -v", as in the following example:
# mount -v
/dev/vx/dsk/rootvol on / type ufs
read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=4ec0000
on Thu Apr 28 16:06:52 2005
Change History
03-May-2005:
Added VxVM 4.1 for Solaris 10 to "Contributing Factors"
Added additional notes and point patch information to "Resolution"
08-Apr-2005:
Further clarifications added to "Relief/Workaround" section (swapvol was removed from examples, reboot 2x Note: was added)
15-Mar-2005:
Clarifications added (volume names ) to "Relief/Workaround" Section, note 4 for Solaris 10 added to Contributing Factors
03-Feb-2005:
Remove point patch information from Workaround
11-Jan-2005:
Add Point Patches for VxVM (Solaris 9) to Relief/Workaround section
30-Jun-2005:
Updated "Resolution" section
07-Sep-2005:
Update Contributing Factors and Resolution sections
05-Dec-2005:
Updated Contributing Factors and Resolution sections, re-release as Resolved
15-Dec-2005:
Updated Contributing Factors and Resolution sections
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-2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. |
|
免费注册
发表于 2006-08-21 09:34
