12-18-2007
The LD determines the RAID level, not the individual disks; so there is no need to specify a RAID level when adding them.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have 2 3510FC arrays, one a JBOD with (7) 146GB drives, and the other with dual RAID controllers, also (7) 146GB drives. The idea was to get 1TB mirrored. Anyway, after installing the Enterprise Storage Manager on a connected V880, I was able to use the "sccli" command and see/configure all the... (7 Replies)
Discussion started by: ridgeback00
7 Replies
2. Solaris
Hi Peeps,
Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it.
Anyone got any ideas on how to remove the EFI label?
Thanks in advance
Martin (2 Replies)
Discussion started by: callmebob
2 Replies
3. Linux
I am on Red Hat Linux 4.7.
I am getting this error message:
Preparing... ###########################################
You have insufficient diskspace in the destination directory (/usr/lib) to
install xxxxxxxxxxxxx. The installation requires at
least 1.5 GB free on this... (2 Replies)
Discussion started by: jxh461
2 Replies
4. UNIX for Advanced & Expert Users
I have a 3510 disk array attached to a T2000 server.
The dmesg command shows disk error as follows and is generated a couple of times during the day
Aug 18 03:35:51 myserver SUNWscsdMonitor: <rctrl6042> Standard General Event, CHL:2 ID:22 Drive NOTICE: Drive Recovered Error - 5F8E1F... (1 Reply)
Discussion started by: Tirmazi
1 Replies
5. Shell Programming and Scripting
Hi Friends,
I want to know the command to add a new file in a existing tar file.
For Ex:
I have a tar file file1.tar with the contents
one.txt
two.txt
three.txt
Now I need to add file four.txt to this existing tar file, how can I do it?
Thanks in advance (4 Replies)
Discussion started by: mr_manii
4 Replies
6. Shell Programming and Scripting
Hi Everybody,
I have an layout file like below
f1 1 char 10,
f2 11 char 2,
f3 13 char 1,
lineend 14 char 1
Their I need to add a new field which would be like
f5 char 3,
f6 char 2
The o/p should be
f1 1 char 10,
f2 11 char 2,
f3 13 char 1,
f5 14 char 3,
f6 17 char 2 (3 Replies)
Discussion started by: mr_manii
3 Replies
7. Shell Programming and Scripting
Hi....
i have two scripts called:
"type" & "selecttype".
In "type" i have only the name of the products ex.: product1 & product2. Now, i have to ADD product3 which includes sub categories: productA, productB, productC, productD, productE, productF. so my New type script (menu) looks as... (1 Reply)
Discussion started by: Netrock
1 Replies
8. Shell Programming and Scripting
I have a data file that looks like this:
0.01 1 3822 4.97379915032e-14 4.96982253992e-09 0
0.01 3822 1 4.97379915032e-14 4.96982253992e-09 0
0.01 2 502 0.00993165137406 993.165137406 0
0.01 502 2 0.00993165137406 993.165137406 0
0.01 4 33 0.00189645523539 189.645523539 0
0.01 33 4... (3 Replies)
Discussion started by: kayak
3 Replies
9. AIX
Hi
Below are the new luns added by the storage team. My cluster setup is a three node HA cluster. I could see the below mentioned luns on all the three nodes :
hdisk26 00084dd0ef986943 None
hdisk27 00084dd0ef988d1f None
and we tried to... (3 Replies)
Discussion started by: newtoaixos
3 Replies
10. UNIX for Beginners Questions & Answers
I have an array in an external file, "array.txt", which contains:
char *testarray={"Zero", "One", "Two", "Three", "Four", "Five", "Six", "Seven", "Eight", "Nine"};I want to be able to add an element to this array, and have that element display, whenever I call it, without having to recompile... (29 Replies)
Discussion started by: ignatius
29 Replies
LEARN ABOUT OPENSOLARIS
did
did(7) Sun Cluster Device and Network Interfaces did(7)
NAME
did - user configurable disk id driver
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.
Disk ID (DID) is a user configurable pseudo device driver that provides access to underlying disk, tape, and CDROM devices. When the
device supports unique device ids, multiple paths to a device are determined according to the device id of the device. Even if multiple
paths are available with the same device id, only one DID name is given to the actual device.
In a clustered environment, a particular physical device will have the same DID name regardless of its connectivity to more than one host
or controller. This, however, is only true of devices that support a global unique device identifier such as physical disks.
DID maintains parallel directories for each type of device that it manages under /dev/did. The devices in these directories behave the same
as their non-DID counterparts. This includes maintaining slices for disk and CDROM devices as well as names for different tape device
behaviors. Both raw and block device access is also supported for disks by means of /dev/did/rdsk and /dev/did/rdsk.
At any point in time, I/O is only supported down one path to the device. No multipathing support is currently available through DID.
Before a DID device can be used, it must first be initialized by means of the scdidadm(1M) command.
IOCTLS
The DID driver maintains an admin node as well as nodes for each DID device minor.
No user ioctls are supported by the admin node.
The DKIOCINFO ioctl is supported when called against the DID device nodes such as /dev/did/rdsk/d0s2.
All other ioctls are passed directly to the driver below.
FILES
/dev/did/dsk/dnsm block disk or CDROM device, where n is the device number and m is the slice number
/dev/did/rdsk/dnsm raw disk or CDROM device, where n is the device number and m is the slice number
/dev/did/rmt/n tape device , where n is the device number
/dev/did/admin administrative device
/kernel/drv/did driver module
/kernel/drv/did.conf driver configuration file
/etc/did.conf scdidadm configuration file for non-clustered systems
Cluster Configuration Repository (CCscdidadm(1M) maintains configuration in the CCR for clustered systems
SEE ALSO
devfsadm(1M), Intro(1CL), cldevice(1CL), scdidadm(1M)
NOTES
DID creates names for devices in groups, in order to decrease the overhead during device hot-plug. For disks, device names are created in
/dev/did/dsk and /dev/did/rdsk in groups of 100 disks at a time. For tapes, device names are created in /dev/did/rmt in groups of 10
tapes at a time. If more devices are added to the cluster than are handled by the current names, another group will be created.
Sun Cluster 3.2 24 April 2001 did(7)