Migrating non DID device in a metaset to DID device


 
Thread Tools Search this Thread
Operating Systems Solaris Migrating non DID device in a metaset to DID device
# 1  
Old 01-18-2010
Migrating non DID device in a metaset to DID device

One of my team colleague mistakenly added non DID device to a metaset in a cluster node and inturn it is again added to concat .

In that metaset all devices are DID devices except only one . is it possible to convert this non DID device in metaset to DID device without recreating the whole stuff ?
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Command to see the logical volume path, device mapper path and its corresponding dm device path

Currently I am using this laborious command lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}' Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies

2. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

4. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

5. AIX

How to find all device on p570 when need do device firmware upgrade?

I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
Login or Register to Ask a Question
scconf_quorum_dev_scsi(1M)				  System Administration Commands				scconf_quorum_dev_scsi(1M)

NAME
scconf_quorum_dev_scsi - Add and remove shared SCSI quorum devices and change various SCSI cluster quorum configuration properties or states. SYNOPSIS
scconf {-a|-c|-r} -q globaldev=devicename otheroptions scconf {-a|-c|-r} -q name=devicename otheroptions DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. A SCSI quorum device is considered to be any Sun Cluster supported, attached storage that is connected to two or more nodes of the cluster. The device must be managed by DID, and the device name that is provided must be a DID device name. The SCSI quorum device has no other properties that can be specified. OPTIONS
The following options are specific to shared disk quorum devices. See scconf(1M) for the list of supported generic options. See scconf_quo- rum_dev_netapp_nas(1M) for options that are specific to NAS quorum devices. The add and remove forms of the command are used to add and remove shared quorum devices to or from the configuration. The change form of the command is used for changing various properties of cluster quorum configuration. The -q quorum-options available for each of the three forms of the command can be used to change the cluster quorum configuration are as follows: Add a shared quorum device: -q -a globaldev=devicename[, node=node,node=node[, ...]] or -q -a name= devicename,type=scsi or -q -a autoconfig[,noop] Change a property or state of quorum configuration: -q -c globaldev=devicename,{maintstate | reset} or -q -c autoconfig[,noop] Remove a shared quorum device: -q -r globaldev=devicename or -q -r name=devicename autoconfig When used with the add form of the command, automatically chooses and assigns one quorum device in the two-node cluster. The quorum device is chosen from the available devices. If a quorum device is already configured, the command aborts. When used with the change form of the command, automatically chooses and assigns one device that replaces all existing quorum devices in the two-node cluster. The quorum device is chosen from the available devices. All available devices in the cluster must be qualified to be a quorum device. The autoconfig suboption does not assess whether an available device is qualified to be a quorum device. If the cluster contains more than two nodes, the autoconfig suboption makes no changes to the quorum configuration. Do not use the autoconfig suboption if you intend to configure a NAS device as quorum. [,noop] Is valid with the autoconfig suboption. The command prints to standard output the list of quorum devices that the autoconfig suboption would add or change. The autoconfig,noop suboption makes no changes to the quorum configuration. When scconf is interrupted or fails while performing quorum-related operations, quorum configuration information can become inconsistent in the cluster configuration database. If an inconsistency occurs, either run the same scconf command again or run it with the reset option to reset the quorum information. With the add form of the command, if a name is specified without a node list, the quorum device is added with a port defined for every node to which the device is attached. But, if a node list is given, at least two nodes must be provided, and each node in the list must be ported to the device. EXAMPLES
Example 1 Adding SCSI Quorum Devices The following scconf commands adds a SCSI quorum device. -a -q globaldev=/dev/did/rdsk/d4s2 or -a -q name=/dev/did/rdsk/d4s2,type=scsi Example 2 Changing SCSI Quorum Devices The following scconf command changes a SCSI quorum device configuration. -c -q globaldev=/dev/did/rdsk/d4s2,reset or -c -q name=/dev/did/rdsk/d4s2,reset Example 3 Removing SCSI Quorum Devices The following scconf command removes the SCSI quorum device. qd1. -r -q globaldev=qd1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scconf_quorum_dev_netapp_nas(1M) Sun Cluster 3.2 10 Apr 2006 scconf_quorum_dev_scsi(1M)