Sponsored Content
Full Discussion: Reg. VXVM
Operating Systems Solaris Reg. VXVM Post 302294341 by Grippo on Thursday 5th of March 2009 04:21:01 AM
Old 03-05-2009
no need for the reboot at all.
simply use vxdiskadm option 4 to remove the disk and then option 5 to insert the new one.
the only thing that will be different is that you will not longer see the boot-block wrapper on the root volume.
 

10 More Discussions You Might Find Interesting

1. Solaris

VxVM

All solaris rescue gurus out there .... I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory. The machine is (was) running Vxvm with the root volume encapsulated. I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies

2. Filesystems, Disks and Memory

vmstat -d with VxVM

I've got a Linux box that I'm pretty sure is having some disk issues. iostat isn't installed, but vmstat is, so i've been trying to use that to do some initial diagnostics while I go through our company's change control process to get iostat installed. The problem I'm having is that the disks... (4 Replies)
Discussion started by: kknigga
4 Replies

3. Solaris

VxVM..anything to worry about in here..

DEVICE TYPE DISK GROUP STATUS c0t0d0s2 sliced rootdisk rootdg online c1t1d0s2 sliced disk01 rootdg online c2t0d0s2 sliced actsvr101 actsvr1dg online c2t2d0s2 sliced actsvr102 actsvr1dg online c2t3d0s2 ... (13 Replies)
Discussion started by: incredible
13 Replies

4. Solaris

VxVM on Solaris.

Hi, Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies

5. Filesystems, Disks and Memory

VxVM and MPxIO

:confused: Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO. If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies

6. Solaris

ZFS and VxVM

Hi community, I've a hard question for you. 1)What are the differences between ZFS and Veritas Volume Manager on Solaris10? 2) what is the difference to manage the internal disks (Mirror)? 3) what is the difference to manage the external disks? 4) What is the difference to manage... (5 Replies)
Discussion started by: Sunb3
5 Replies

7. Solaris

No of volumes in vxvm

Anyone knows that how many volumes can be created in a Diskgroup? Thanks in advance... (1 Reply)
Discussion started by: bpsunadm
1 Replies

8. Solaris

vxvm

hi all, how can we check whether vxvm is installed in our system or not in solaris? Thanks in advance dinu (4 Replies)
Discussion started by: dinu
4 Replies

9. 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

10. Solaris

Fsck in vxvm

Hi, When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also. compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS. Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 06:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy