VxVm的一个问题

东方蜘蛛

也有可能是sd.conf导致的，去看看两边的这个文件内容一致不！

东方蜘蛛

Document Audience: SPECTRUM
Document ID: 73683
Title: Veritas Volume Manager: Fails to initalize disk devices over 1TB in size
Copyright Notice: Copyright © 2006 Sun Microsystems, Inc. All Rights Reserved
Update Date: Mon May 15 00:00:00 MDT 2006
Products:  VERITAS Volume Manager 3.5 Software,  VERITAS Volume Manager 4.0 Software
Technical Areas:  Software Troubleshooting,  LVM (Logical Volume Management)

--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

Keyword(s):EFI, VxVM, SDS, read, Disk, geometry, errno, 0x6, failed, offline

Problem Statement: Top

An attempt to initialize a disk in Veritas Volume Manager (VxVM) (either through vxdiskadm or by vxdisksetup) fails with one of the following messages:

  The Volume Manager is now reconfiguring (partition phase)...

   Volume Manager: Partitioning c1t1d0 as a new disk.

   The partitioning of c1t1d0 failed.

The following messages are seen with VxVM 4.0:

# /usr/lib/vxvm/bin/vxdisksetup -i c1t12d0

prtvtoc: /dev/vx/rdmp/c1t12d0s2: Unable to read Disk geometry errno = 0x6

# vxdiskadm fails with following error:

<SNIP of vxdiskadm output>

Adding disk device c1t12d0 to disk group testdg with disk name testdg03.
VxVM  ERROR V-5-2-87 Adding disk device c1t12d0 failed.
VxVM vxdg ERROR V-5-1-10128  Disk device is offline

All current versions of Veritas Volume Manager, up to and including 4.0, are affected.

Resolution: Top

Devices larger than 1TB are labeled with EFI-format disk labels instead of the older VTOC style. This is a requirement for >1TB disk devices, as VTOC only supports up to ~900GB. A device larger than this will automatically be assigned an EFI label, and this CAN NOT be changed.

In addition, smaller disks MAY be assigned an EFI label, although a VTOC style of label would work. In these situations, VxVM would fail to initialize these disks as well. VxVM does not support EFI labels on any size disk until VxVM 4.1.

This problem is documented in Bug ID 4794934, and is fixed in VxVM 4.1 but it is supported only on Solaris 10. Veritas supports EFI disks on Solaris 10 only. As of today there no plans for this to be supported on Solaris 9 and below.

Temporary Workaround: Top

Temporary workaround(s)

1. Use Solaris[TM] Volume Manager
(SVM) on Solaris[TM] 9 or above, which is EFI aware
with required patches.

2. Split the 1TB lUN in half (using the hardware RAID functions), creating
two smaller LUNS, then use VXVM to create a concatenation using
the two smaller LUNS.
This process creates a 1TB volume using Volume Manager.

Additional Information: Top

Storage Foundation 4.1 Release Notes available at

http://webhome.sfbay/partnersoft ... ocuments/index.html

contains the following Info regarding EFI Label:

Extensible Firmware Interface (EFI) Support On systems that are running a 64-bit kernel, Solaris 9 and 10 Operating Systems provide support for disks that are larger than 1 terabyte. Disks of this size are formatted with the EFI disk label rather than the VTOC disk label. A number of commands and libraries have been modified to provide this support. Veritas supports EFI disks on Solaris 10 only.

Converting a Multipathed Disk
Under Solaris 10 when converting a multipathed disk that is smaller than
1TB from a VTOC label to an EFI label, you must issue a format -e command for each path. For example, if a node has two paths, c1t2d0s2 and c2t2d0s2, you need to apply the format -e command to each of the two paths.

[ 本帖最后由 东方蜘蛛 于 2006-9-10 22:54 编辑 ]

lo-so

原因是两台机器识别出来的disk的编号不一样.

根据你贴的信息
在A机上是新盘是:
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_5 auto            -            -            error
EMC_CLARiiON0_6 auto            -            -            error
EMC_CLARiiON0_13 auto            -            -            error
EMC_CLARiiON0_20 auto            -            -            error


EMC_CLARiiON0_17是以前的盘,只是在加盘后名字变了而已!