10 More Discussions You Might Find Interesting
1. AIX
Good afternoon!
Help with a solution
I have AIX 7.1
works through vios
I expanded Lun
that it is necessary to make that aix saw this change and to expand the section lvm
Sorry for my English (1 Reply)
Discussion started by: iformats
1 Replies
2. Solaris
Hi All
I am having VxVm on two Solaris hosts. host1 is using disk group dgHR. right now this server went down due to hardware fault. Not I need to import this dgHR into host2 server. Please let me know the procedure for the same. (1 Reply)
Discussion started by: amity
1 Replies
3. Solaris
Dear all,
i want to get the LUN ID for some disks in solaris 10
what commands options for the MPXIO and inq i want these utilities only
because i don't have solution enabler or powerpath
BR, (1 Reply)
Discussion started by: maxim42
1 Replies
4. AIX
Hi,
I am not getiting lun id information on VIO Server. I have used the command fget_config command.
just showing # prompt.
I would like know wheather any other command is there equiv of fget_config
which will display lun id? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. Solaris
How to share a diskgroup in veritas. (1 Reply)
Discussion started by: padmaja
1 Replies
6. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
7. Solaris
hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies
8. Solaris
Hello experts..
I am unable to import a disk group using vxdg . Is there any other command to import a disk group..
Thanks in advance.. (4 Replies)
Discussion started by: younus_syed
4 Replies
9. AIX
I have been ask to write a script to show what phyical disks are linked to what luns. By host name. I was hoping someone had some ideas on how to do this. I am from a linux background and am struggling a bit here...lol...I have been given one command to help me out....lsmap..Anyhelp would be... (3 Replies)
Discussion started by: jameszak
3 Replies
10. Red Hat
Hello,
I'm trying to help a guy out on a VMWARE server, running what looks like a cut down version of redhat? 2.4.9-vmnix2 ...
Bascially the box serves vm clients via allocating a LUN from a SAN.. to cut a long story short, I need to find out which SAN the luns are comming from (could be 1... (0 Replies)
Discussion started by: itsupplies
0 Replies
LEARN ABOUT NETBSD
bioctl
BIOCTL(8) BSD System Manager's Manual BIOCTL(8)
NAME
bioctl -- RAID management interface
SYNOPSIS
bioctl device command [arg [...]]
DESCRIPTION
RAID device drivers which support management functionality can register their services with the bio(4) driver. bioctl then can be used to
manage the RAID controller's properties.
COMMANDS
The following commands are supported:
show [disks | volumes]
Without any argument by default bioctl will show information about all volumes and the logical disks used on them. If
disks is specified, only information about physical disks will be shown. If volumes is specified, only information about
the volumes will be shown.
alarm [disable | enable | silence | test]
Control the RAID card's alarm functionality, if supported. By default if no argument is specified, its current state
will be shown. Optionally the disable, enable, silence, or test arguments may be specified to enable, disable, silence,
or test the RAID card's alarm.
blink start channel:target.lun | stop channel:target.lun
Instruct the device at channel:target.lun to start or cease blinking, if there's ses(4) support in the enclosure.
hotspare add channel:target.lun | remove channel:target.lun
Create or remove a hot-spare drive at location channel:target.lun.
passthru add DISKID channel:target.lun | remove channel:target.lun
Create or remove a pass-through device. The DISKID argument specifies the disk that will be used for the new device, and
it will be created at the location channel:target.lun. NOTE: Removing a pass-through device that has a mounted filesys-
tem will lead to undefined behaviour.
check start VOLID | stop VOLID
Start or stop consistency volume check in the volume with index VOLID. NOTE: Not many RAID controllers support this fea-
ture.
create volume VOLID DISKIDs [SIZE] STRIPE RAID_LEVEL channel:target.lun
Create a volume at index VOLID. The DISKIDs argument will specify the first and last disk, i.e.: 0-3 will use the disks
0, 1, 2, and 3. The SIZE argument is optional and may be specified if not all available disk space is wanted (also
dependent of the RAID_LEVEL). The volume will have a stripe size defined in the STRIPE argument and it will be located
at channel:target.lun.
remove volume VOLID channel:target.lun
Remove a volume at index VOLID and located at channel:target.lun. NOTE: Removing a RAID volume that has a mounted
filesystem will lead to undefined behaviour.
EXAMPLES
The following command, executed from the command line, shows the status of the volumes and its logical disks on the RAID controller:
$ bioctl arcmsr0 show
Volume Status Size Device/Label RAID Level Stripe
=================================================================
0 Building 468G sd0 ARC-1210-VOL#00 RAID 6 128KB 0% done
0:0 Online 234G 0:0.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
0:1 Online 234G 0:1.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
0:2 Online 234G 0:2.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
0:3 Online 234G 0:3.0 noencl <WDC WD2500YS-01SHB1 20.06C06>
To create a RAID 5 volume on the SCSI 0:15.0 location on the disks 0, 1, 2, and 3, with stripe size of 64Kb on the first volume ID, using all
available free space on the disks:
$ bioctl arcmsr0 create volume 0 0-3 64 5 0:15.0
To remove the volume 0 previously created at the SCSI 0:15.0 location:
$ bioctl arcmsr0 remove volume 0 0:15.0
SEE ALSO
arcmsr(4), bio(4), cac(4), ciss(4), mfi(4)
HISTORY
The bioctl command first appeared in OpenBSD 3.8, it was rewritten for NetBSD 5.0.
AUTHORS
The bioctl interface was written by Marco Peereboom <marco@openbsd.org> and was rewritten with multiple features by
Juan Romero Pardines <xtraeme@NetBSD.org>.
BSD
March 16, 2008 BSD