Issue while Extending file system in vxvm

Post the entire output of root@myers# vxdisk -o alldgs -e list

Not just the ones in the DG. If the new disk do not show "error" then you can use vxdisksetup -i to initialize.

I agree with Riaan, post the entire output of vxdisk list for new 4 luns.

What I see is you are unable to label them, are these fresh disks from storage ? (double check if these disks doesn't contain any data)

Check if these disks are not zoned to any other host or if zoning from SAN switches is done correctly for this host to have write access, or these disks were used in cluster before which had any IOFencing on it (SCSI 3 PR reservations) which is blocking your access on the disk.

G

root@myers# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
emcpower22s2 auto:cdsdisk    VRP_PRD_sapcent_dg01  VRP_PRD_sapcent_dg online
emcpower23s2 auto:cdsdisk    emcpower23s2  VRP_PRD_ora_data_dg online
emcpower24s2 auto:cdsdisk    emcpower24s2  VRP_PRD_ora_data_dg online
emcpower25s2 auto:cdsdisk    emcpower25s2  VRP_PRD_ora_data_dg online
emcpower26s2 auto:cdsdisk    emcpower26s2  VRP_PRD_ora_data_dg online
emcpower27s2 auto:cdsdisk    emcpower27s2  VRP_PRD_ora_bin_dg online
emcpower28s2 auto:cdsdisk    VRP_PRD_ora_arch_dg01  VRP_PRD_ora_arch_dg online

=====================================================================

I am unable to view the new luns in vxdisk o/p.

Yes, those luns are assigned fresh from storage.

But, as i checked in Partition table,

format> p

PARTITION MENU:
        0      - change `0' partition
        1      - change `1' partition
        2      - change `2' partition
        3      - change `3' partition
        4      - change `4' partition
        5      - change `5' partition
        6      - change `6' partition
        7      - change `7' partition
        select - select a predefined table
        modify - modify a predefined partition table
        name   - name the current table
        print  - display the current table
        label  - write partition map and label to the disk
        !<cmd> - execute <cmd>, then return
        quit
partition> p
Current partition table (default):
Total disk cylinders available: 29158 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm       0                0         (0/0/0)            0
  1       swap    wu       0                0         (0/0/0)            0
  2     backup    wu       0 - 29157       26.69GB    (29158/0/0) 55983360
  3 unassigned    wm       0                0         (0/0/0)            0
  4 unassigned    wm       0                0         (0/0/0)            0
  5 unassigned    wm       0                0         (0/0/0)            0
  6        usr    wm       0 - 29157       26.69GB    (29158/0/0) 55983360
  7 unassigned    wm       0                0         (0/0/0)            0

================================================

Slice 6 is showing 26.69 GB.Is that due to which I was unable to label it?

run

vxdclt enable

vxdisk scandisks

then check

vxdisk -o alldgs list

root@myers# vxdisk -o alldgs list
DEVICE       TYPE            DISK         GROUP        STATUS
emcpower22s2 auto:cdsdisk    VRP_PRD_sapcent_dg01  VRP_PRD_sapcent_dg online
emcpower23s2 auto:cdsdisk    emcpower23s2  VRP_PRD_ora_data_dg online
emcpower24s2 auto:cdsdisk    emcpower24s2  VRP_PRD_ora_data_dg online
emcpower25s2 auto:cdsdisk    emcpower25s2  VRP_PRD_ora_data_dg online
emcpower26s2 auto:cdsdisk    emcpower26s2  VRP_PRD_ora_data_dg online
emcpower27s2 auto:cdsdisk    emcpower27s2  VRP_PRD_ora_bin_dg online
emcpower28s2 auto:cdsdisk    VRP_PRD_ora_arch_dg01  VRP_PRD_ora_arch_dg online
emcpower29s2 auto            -            -            nolabel
emcpower30s2 auto            -            -            nolabel
emcpower33s2 auto            -            -            nolabel
emcpower34s2 auto            -            -            nolabel

===================================================

But, when I try to initialze it shows the below error,

root@myers# vxdisksetup -i emcpower29s2 format=cdsdisk
bash: vxdisksetup: command not found
root@myers# /etc/vx/bin/vxdisksetup -i emcpower29s2 format=cdsdisk
VxVM vxdisksetup ERROR V-5-2-2206 emcpower29s2: An invalid device address was specified; it must be of
the form cCtTdD, mcCtTdD or <enclosurename>_<diskno> where

    C = host bus adapter controller number
    T = target device controller number, if used
    D = logical unit (disk) number within target device controller

    <enclosurename> is the logical name of the enclosure to which the
                    disk belongs
    <diskno> is the logical number of the disk

How to proceed?

Ok, now you can proceed to label as we can see the disks have no label and VXVM reports it.

You'll need to troubleshoot the labeling with OS support.

Are you still facing errors while labelling disk ?

G

I have seen the same issue some years ago when Storage Admins assigned new luns to a server.

It turned out to be incorrect Lun settings at EMC array level (they never told us what exactly).

Ask storage admins to compare lun settings of working luns with newly added luns.

Required LUN/Array settings are listed in SF Host and Storage Configuration Guide for Dynamic Multi-Pathing :  http://www.symantec.com/docs/TECH47728

Have you tried Format -> type -> Autoconfigure and then labelling? 

Agree with other that if you cannot label from O/S then you need to address this before putting under VxVM control, but for the vxdisksetup command you need to take the s2 off the end so command should be:

vxdisksetup -i emcpower29 format=cdsdisk

Mike