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
fence_scsi(8)						      System Manager's Manual						     fence_scsi(8)

NAME
fence_scsi - I/O fencing agent for SCSI persistent reservations SYNOPSIS
fence_scsi [OPTION]... DESCRIPTION
fence_scsi is an I/O fencing agent that uses SCSI-3 persistent reservations to control access to shared storage devices. These devices must support SCSI-3 persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" subcommand. The fence_scsi agent works by having each node in the cluster register a unique key with the SCSI devive(s). Once registered, a single node will become the reservation holder by creating a "write exclusive, registrants only" reservation on the device(s). The result is that only registered nodes may write to the device(s). When a node failure occurs, the fence_scsi agent will remove the key belonging to the failed node from the device(s). The failed node will no longer be able to write to the device(s). A manual reboot is required. In the cluster environment unfence action should be configured also. Keys are either be specified manually (see -k option) or generated automatically (see -n option). Automatic key generation requires that cman be running. Keys will then be generated using the cluster ID and node ID such that each node has a unique key that can be determined by any other node in the cluster. Devices can either be specified manually (see -d option) or discovered automatically. Multiple devices can be specified manually by using a comma-separated list. If no devices are specified, the fence_scsi agent will attempt to discover devices by looking for cluster volumes and extracting the underlying devices. Devices may be device-mapper multipath devices or raw devices. If using a device-mapper multipath device, the fence_scsi agent will find the underlying devices (paths) and created registrations for each path. OPTIONS
-o action Fencing action. This value can be "on", "off", "status", or "metadata". The "on", "off", and "status" actions require either a key (see -k option) or node name (see -n option). For "on", the agent will attempt to register with the device(s) and create a reserva- tion if none exists. The "off" action will attempt to remove a node's key from the device(s). The "status" action will report whether or not a node's key is currently register with one or more of the devices. The "metadata" action will display the XML meta- data. The default action if "off". -d devices List of devices to use for current operation. Devices can be comma-separated list of raw device (eg. /dev/sdc) or device-mapper mul- tipath devices (eg. /dev/dm-3). Each device must support SCSI-3 persistent reservations. -f logfile Log output to file. -n nodename Name of the node to be fenced. The node name is used to generate the key value used for the current operation. This option will be ignored when used with the -k option. -k key Key to use for the current operation. This key should be unique to a node. For the "on" action, the key specifies the key use to register the local node. For the "off" action, this key specifies the key to be removed from the device(s). -H delay Wait X seconds before fencing is started (Default Value: 0) -a Use the APTPL flag for registrations. This option is only used for the "on" action. -h Print out a help message describing available options, then exit. -v Verbose output. -V Print out a version message, then exit. STDIN PARAMETERS
agent = "param" This option is used by fence_node(8) and is ignored by fence_scsi. nodename = "param" Same as -n option. action = "param" Same as -o option. devices = "param" Same as -d option. logfile = "param" Same as -f option key = "param" Same as -k option. delay = "param" Same as -H option. aptpl = "1" Enable the APTPL flag. Default is 0 (disable). SEE ALSO
fence(8), fence_node(8), sg_persist(8), vgs(8), cman_tool(8), cman(5) fence_scsi(8)