Sponsored Content
Operating Systems Solaris ( VxVM ) How to add the removed disk back to previous disk group Post 302308379 by waibabe on Saturday 18th of April 2009 01:09:50 AM
Old 04-18-2009
( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by

#vxdg -g testdg -k rmdisk testdg02

But i got error when i -k adddisk



bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none - - online invalid
c4t129d0s2 auto:cdsdisk - - online
c4t129d1s2 auto:cdsdisk testdg01 testdg online
- - testdg02 testdg removed was:c4t129d0s2


bash-2.03# vxdg -g testdg -k adddisk testdg02=c4t129d0

VxVM vxdg ERROR V-5-1-2349 Device c4t129d0s2 appears to be owned by disk group testdg.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

VxVM disk/lun grow

hi, i have a volume on a LUN of an EMC-storage and i need to increase the size. i could increase the size of the LUN on the EMC, i could increase the size of the disk for solaris, but how can i tell the veritas volume manager that the disk is larger now? what i've done: 1. LUN on EMC 2.... (3 Replies)
Discussion started by: pressy
3 Replies

2. Solaris

How to add disk into Striped Volume VxVM

VxVM: How to add one more disk into v08 the stripe should change from 7/128 to 8/128 v v08 - ENABLED ACTIVE 8954292224 SELECT v08-01 fsgen pl v08-01 v08 ENABLED ACTIVE 8954292480 STRIPE 7/128 RW sd bkpdg35-01 v08-01 bkpdg35 17216 ... (0 Replies)
Discussion started by: geoffry
0 Replies

3. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

4. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

5. Solaris

Disk Storage Need to Add more Disk

Hi, Anyone can help me, just want to confirm, if possible adding a disk storage that we have a RAWDATA with +ASM in our database. If possible, what would you recommend "workaround used" from us to do and the preparation. And also how long the downtime will take. Our disk continuous to grow,... (0 Replies)
Discussion started by: fpalero
0 Replies

6. Solaris

Unable to add disk to VG group.

Hi, I am new to solaris administration. I have scan the new EMC SAN disk. I am able to see the disk when i run the powermt display dev=all command o/p. I want to format the disk and add file system to that disk. Can have formated the disk. and this the o/p of my format bash-3.00# prtvtoc... (3 Replies)
Discussion started by: jpkumar10
3 Replies

7. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

8. Emergency UNIX and Linux Support

VxVM not able to see new disk

I have VxVM 5.1 running on Solaris-10. I have to increase a application file-system and storage team gave me a lun. After scanning scsi port by cfgadm, I can see them in format output. I labelled it, but I am not able to see them in "vxdisk list". I already tried commands --> vxdctl enable... (4 Replies)
Discussion started by: solaris_1977
4 Replies

9. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies

10. Solaris

How to clear a removed single-disk pool from being listed by zpool import?

On an OmniOS server, I removed a single-disk pool I was using for testing. Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore. # zpool import pool: fido id: 7452075738474086658 state: FAULTED status: The pool was last... (11 Replies)
Discussion started by: priyadarshan
11 Replies
vxdisksetup(1M) 														   vxdisksetup(1M)

NAME
vxdisksetup, vxdiskunsetup - configure a disk for use with Veritas Volume Manager SYNOPSIS
vxdisksetup [-ifB] disk_address [attribute ...] vxdisksetup [-ifB] disk_address format=hpdisk [attribute ...] vxdisksetup [-if] disk_address format=cdsdisk [attribute ...] /etc/vx/bin/vxdiskunsetup [-C] [-F] disk_address... DESCRIPTION
The vxdisksetup command configures the disk for use by Veritas Volume Manager (VxVM). vxdisksetup is called by the vxdiskadd command as part of initial disk configuration. It is not typically necessary to call this command directly. Note: In release 4.0 of VxVM, the behavior of the vxdisksetup command has been changed so that it only creates auto-configured disks (with a disk access type of auto; see vxdisk(1M)), which can have one of the following formats: cdsdisk The disk is formatted as a CDS disk that is suitable for moving between different operating systems. This is the default format for non-EFI disks (provided that the -i option is used to write the disk header). It is not suitable for boot disks or EFI disks. Note: As the CDS format is applied to the entire disk and is unsuitable for boot disks, options and attributes that relate to partitions, slices or booting are not applicable. The CDS format is also incompatible with EFI disks. hpdisk The disk is formatted to include a private region that VxVM uses to store configuration information. Following the private region, the remainder of the disk forms the public region from which subdisks can be allocated. This format can be applied to disks that can be used to boot the system. If the disk is not initialized as a boot disk, space is reserved on the disk to allow it to be converted to cdsdisk format if required. The hpdisk format is the default for EFI disks. none The disk is unformatted. Note: This value may be displayed, but it cannot be set as a valid format. The vxdiskunsetup command reverses the configuration done by vxdisksetup and makes the specified disks unusable by VxVM. vxdiskunsetup can be applied only to VxVM-initialized disks that are not in use within an imported disk group. The disk_address argument passed to vxdisksetup or to vxdiskunsetup directs the command to the device that corresponds to the disk being operated upon. The address should be provided in the form c#t#d#, which define a controller number (c#), a SCSI target ID (t#), and a SCSI logical unit number (d#). Each number is specified in decimal and can be multiple digits. If the disks are named using the enclosure based naming scheme, the address usually takes the form enclosurename_diskno. The name must reference a valid disk under the /dev/vx/rdmp directory. The vxdiskunsetup command operates by removing the public and private regions that were created by the last invocation of vxdisksetup on the specified disks. After this operation, those disks are converted from the online to the error state state (as displayed by vxdisk list). The /etc/default/vxdisk file can be used to set the default values of the format and privlen attributes for the vxdisk and vxdisksetup com- mands. Values in this file override inbuilt values, and may themselves be overridden by values specified on the command line. For details, see the vxdisk(1M) manual page. Note: When vxdisksetup is executed on an HP IPF (IA64) system, the target disk is either configured or deconfigured as an EFI partitioned disk. The action that is taken depends on whether the -B option is specified, and whether the disk is already formatted as an EFI parti- tioned disk: o If the -B option is specified, and the disk is not already formatted as an EFI disk, the idisk(1M) utility is called to format the disk as an EFI partitioned disk. The partitioning creates an EFI header in the first 1K block, a 100MB partition (or slice) 1, and partition 2 (the HP-UX partition) on the remainder of the disk. If the vxbootsetup(1M) command is subsequently used to configure the disk as a boot disk, partition 1 is populated with an EFI file system, which contains the boot programs that are needed by an HP IPF system, and the HP-UX partition (partition 2) is set up as a logical simple VxVM disk with the same layout as a non-EFI disk. When vxdisksetup has completed setting up an EFI disk, the resulting disk must be addressed using the s2 suffix to select the logical sim- ple VxVM disk. o If the -B option is not specified and the target disk is currently formatted as an EFI partitioned disk, any EFI formatting is destroyed, and the disk is initialized as a non-EFI partitioned disk. OPTIONS
-B Initializes the Veritas Volume Manager private region to begin at block number 2144. This block is designated as the private region offset for a Veritas Volume Manager root disk. Without this option, the private region is initialized to start at the default block number 128. Note: This option is not supported for cdsdisk format disks. -C vxdiskunsetup usually does not operate on disks that appear to be imported by some other host (for example, a host that shares access to the disk). In this case, the -C option can be specified to force de-configuration of the disk, effectively removing the host locks that were detected by vxdiskunsetup. -f Forces a disk to be initialized even if it is a member of a deported disk group. -F By default, the vxdiskunsetup command only operates on online disks. It does not operate on disks that are imported or offline. This option forces an unsetup operation to be performed on such disks. -i Writes a disk header to the disk, initializes the private region of the disk and makes the disk directly usable (as a new disk in a disk group, for example). Note: A disk that is a member of an imported disk group cannot be initialized. The command also fails if the disk is a member of a deported disk group. The -f option can be used to override the latter restriction. ATTRIBUTES
You can specify attributes to affect the layout strategy used by vxdisksetup. CAUTION: Take great care when using these attributes as they can render a disk unusable by VxVM. config Sets up kernel logs or configuration databases on the disk. This attribute has the opposite effect to the noconfig attribute. This is the default behavior if the -i option is specified. Otherwise, the attribute is ignored. noconfig Prevents setting up kernel logs or configuration databases on the disk. The size of the default private region is set to 160 blocks, which is the minimum allowed private region size. noconfig is ignored unless the -i option is specified. noreserve Do not reserve space for conversion to other formats such as cdsdisk. privlen=length Specifies the length of the private region of the disk. The default size of this area is 32MB. The maximum possible size of the private region is 524288 blocks. For cdsdisk format disks, privlen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. privoffset=offset Indicates the sector offset of the private region on the disk. The default value for the private region offset is block number 128 for non-boot disks and block number 2144 for boot disks. For cdsdisk format disks, privoffset is silently rounded up to the nearest multiple of 8KB that is larger than or equal to 128KB if it is not already a multiple of 8KB or if its value is less than 128KB. publen=length Specifies the length of the public region of the disk. This defaults to the size of the disk minus the private area on the disk. For cdsdisk format disks, publen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. puboffset=offset Sets the offset on the disk where the public region starts. By default, this is past the end of the private region. For the hpdisk format, 128 blocks of disk space are reserved at the end of the private region unless this is overridden by the value of puboffset or the -B option is specified. The reserved space allows for later conversion to the cdsdisk format. For cdsdisk format disks, puboffset is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. EXAMPLES
To initialize a disk for regular use, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 To initialize a disk for normal use, but set the private region size to 1MB instead of the default size of 32MB, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 privlen=1m Force deconfiguration of a VxVM-initialized disk, c0f4d0: /etc/vx/bin/vxdiskunsetup -C c0t4d0 NOTES
The default private region size increased from 512KB to 1MB in release 3.2, and from 1MB to 32MB in release 5.0. FILES
/etc/default/vxdisk Defaults file used by the vxdisk and vxdisksetup utilities. SEE ALSO
vxcdsconvert(1M), vxdisk(1M), vxdiskadd(1M), vxintro(1M) VxVM 5.0.31.1 24 Mar 2008 vxdisksetup(1M)
All times are GMT -4. The time now is 03:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy