11-28-2016
Quote:
Originally Posted by
lckdanny
Thanks for your help, I know that it need a SCSI device to control the I/O but I don't where to add it under Integrated Virtualization Manager.
You create it on the VIOS, not the IVM. You need to create a so-called "vhost". Here is a link where, as far as i saw in overviewing it, everything necessary is described:
Virtual SCSI.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. AIX
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies
2. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
3. AIX
hello Folks,
my vio:
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003
VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies
4. AIX
Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines.
Now, on two... (2 Replies)
Discussion started by: rwesterik
2 Replies
5. Red Hat
Hi Everyone,
I have added new Virtual disk to OS. The main point is I need to bring this whole Disk into LVM control, is it necessary to partition the disk using fdisk command and assign partition type as '8e', or can I directly add that disk into LVM, by running pvcreate command with out... (2 Replies)
Discussion started by: bobby320
2 Replies
6. AIX
:wall::wall::wall:
1. I have created an LPAR in the HMC.
2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group.
3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS)
Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
Discussion started by: Dallasguy7
3 Replies
7. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
8. Solaris
I added a disk to a zpool using "zpool add diskname"
My intention was mirror a zpool disk that no mirror; that is a zpool with only one disk. I did not issue the right command. Now, the disk has been added successfully but I cannot remove nor detach it as Solaris 11 thinks it has data on it... (14 Replies)
Discussion started by: LittleLebowski
14 Replies
9. AIX
hi all i have entered Aix environment 4 months had experienced in linux
what i am facing is i am unable to do sort of RnD with aix like
installation on my own, creating vgs managing networks, the VIOS, storage,lpars,
So we have a setup here almost all are in live production environment
with... (4 Replies)
Discussion started by: vax
4 Replies
10. AIX
Hi Guys,
I have fresh new installed VIO 2.2.3.70 on a p710, 3 physical SAS disks, rootvg on hdisk0
and 3 VIO clients through vscsi, AIX7.1tl4 AIX6.1tl9 RHEL6.5ppc, each lpar has its rootvg installed on a LV on datavg (hdisk2) mapped to vhost0,1,2
There is no vg on hdisk1, I use it for my... (1 Reply)
Discussion started by: frenchy59
1 Replies
LEARN ABOUT DEBIAN
scsi-spin
scsi-spin(8) System Manager's Manual scsi-spin(8)
NAME
scsi-spin - spin up and down a SCSI device
SYNOPSIS
scsi-spin [-options...] [device]
DESCRIPTION
scsi-spin let the user to manually spin up and down a SCSI device.
This command is particularly useful if you've got noisy (or hot) drives in a machine that you rarely need to access. This is not the same
as the kernel patch that's floating around that will automatically spin down the drive after some time. scsi-spin is completely manual,
and spinning down a drive that's in use, especially the one containing the scsi-spin binary, is probably a really bad idea.
To avoid running in trouble with such cases, scsi-spin verifies that the device to work on is not currently in use by scanning the mounted
file system description file for a partition living on it and issue an error if this the case.
OPTIONS
-u, --up
spin up device.
-d, --down
spin down device.
-e, --loej
load or eject medium from drive (use along with -u or -d )
-w, --wait=[n]
wait up to n seconds for the spin up/down command to complete. Default is to return immediately after the command was sent to the
device. Either repeat -w n times or set n to define the time to wait before to report a timeout.
-l, --lock
prevent removal of medium from device.
-L, --unlock
allow removal of medium from device.
-I, --oldioctl
use legacy ioctl interface instead of SG_IO to dialog with device (could not be supported on all platforms). -e and -w are not
allowed with this option.
-v, --verbose=[n]
verbose mode. Either repeat -v or set n accordingly to increase verbosity. 1 is verbose, 2 is debug (dump SCSI commands and Sense
buffer).
-f, --force
force spinning up/down the device even if it is in use.
-n, --noact
do nothing but check if the device is in use.
-p, --proc
use /proc/mounts instead of /etc/mtab to determine if the device is in use or not.
device the device is any name in the filesystem which points to a SCSI block device (sd, scd) or generic SCSI device (sg). See section
below.
SCSI devices naming convention
Old kernel naming convention
It is typically /dev/sd[a-z] , /dev/scd[0-9]* or /dev/sg[0-9]*.
scsidev naming convention
It is typically /dev/scsi/s[rdg]h[0-9]*-e????c?i?l? or /dev/scsi/<aliasname>.
devfs naming convention
It is typically /dev/scsi/host[0-9]/bus[0-9]/target[0-9]/lun[0-9]/disc (same for cd and generic devices) or short name
/dev/sd/c[0-9]b[0-9]t[0-9]u[0-9] when devfsd "new compatibility entries" naming scheme is enabled.
SEE ALSO
scsiinfo(8), sg_start(8), sd(4), proc(5),
AUTHORS
Eric Delaunay <delaunay@debian.org>, 2001
Rob Browning <rlb@cs.utexas.edu>, 1998
03 September 2001 scsi-spin(8)