take care with your none/none disks, since you are running oracle these may be used by asm as raw disks, ask your oracle admin
I wrote a little script that reads some kind of id from asm disks, to help me find the relation from lpar to vio disks for asm luns easier
try to run it, a none asm disk should not be listed, to make sure run
Code:
oraid hdiskx
, non asm disks should return 00000000
Code:
cat /usr/bin/oraid
#!/usr/bin/ksh
if [ -z "$1" ]
then
lspv | awk '/none/{print $1}' | while read i ; do echo $i $(od -A n -j 12 -N 4 -x /dev/$i | sed 's/ //g') ; done
else
od -A n -j 12 -N 4 -x /dev/$1 | sed -e 2d -e 's/ //g'
fi
but ask your oracle admin anyways, since I don't want to be responsible that you screw up your database
ok, I am having a seriouse problem!
I can not wite in my landguidge, I live in sweden but I seem to have an american keyboard layout so I cant write some letters and all the key commands are all messed up. Does anyone know where I can find a swedisch keyboard layout? (3 Replies)
I try to solve the problem https://www.unix.com/showthread.php?p=86595 use stack hack method, I am puzzled the stack layout.
under vc6.0, the following code work(in release mode).
#include <stdio.h>
void change()
{
int x;
int j;
(&x) = 5; // if in debug mode, change to (&x) = 5;... (1 Reply)
Apologize if I hurt anyone's head with my questions, I'm entirely new to Unix and my office here doesn't offer any training just learn as you go. Anyways they asked me to get a disk layout of one of our servers and gave me this as an example the lables are assumptions
Disk ... (2 Replies)
I have a fixed width source file like this( it has 5 different record types identified by bolded numbers)
N5101ABCD 9820398 2983287
N5102 9s9923 00000000 00
N5103
N5101TTT 9843438 9494994
N5104 sdsd
N5101YYY 7777777 1111111
I need to have like this:
N5101ABCD ... (2 Replies)
Hi
I am unable to understand the disk layout of one of my disk attached to v240. This is newly installed system from jumpstart.
I am unable to see the free space on backup slice 2 and there are 0 to 8 slices listed when I run format and print the disk info, also there is no reference of... (9 Replies)
I am trying to build a veritas volume similar to an existing volume on another server. The output on source server is:
usbtor12# vxprint -hrtg appdg
v anvil_sqlVOL - ENABLED ACTIVE 629145600 SELECT - fsgen
pl anvil_sqlVOL-01 anvil_sqlVOL ENABLED ACTIVE 629145600... (3 Replies)
Hi Gurus,
I've a sample output from a script with a header as shown below.
The formatting is a little bit out of alignment when it's sent out via email.
Sample output:
Label Date New Data #AB Removed #CD Net Change
Statistic 2012-06-03 21807 mb 206 ... (3 Replies)
I have a B.11.31 U ia64 system where I swremove the disk driver "SerialSCSI-00 B.11.31.1303 PCI-X/PCI-E SerialSCSI" (by mistake). afterwards the system won;t boot because of the missing disk drivers. I'm trying to recover my kernel by using the image HP-ux_11_31_disc_1.iso
Run an Expert... (1 Reply)
Hi all,
I have a EFI disk and it is use in zfs pool.
partition> p
Volume: rpool
Current partition table (original):
Total disk sectors available: 1172107117 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 usr wm ... (8 Replies)
Discussion started by: javanoob
8 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)
12-14-2011
