That means your hdisks are connected to the P1-C1 and P1-C4 adapters:
I'm betting that your tape and/or DVD drive is connected to this RAID controller:
For your own benefit, you can run those lsdev and lscfg commands against them and find out.
I have a script running remotely using viosvrcmd command on hmc to back up the VIO servers. these are the steps involved
1. Mount the NFS directory on to the VIO server
2. run backupios command
3. un mount the directory
I am stuck up in the 3rd step. I am not able to unmount the nfs... (6 Replies)
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO.
On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes
Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
We've got two datacenters and in every datacenter 2 VIOs.
The VIO manages the I/O of the LPARs. So: Is it possible to reboot the VIO without shuting down an LPAR:wall: (4 Replies)
Hi Team,
My new build configuration always looking for the files from the build where i copied from.
please help me to resolve this.
I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development
I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
LEARN ABOUT DEBIAN
mfi
MFI(4) BSD Kernel Interfaces Manual MFI(4)NAME
mfi -- LSI MegaRAID SAS driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device pci
device mfi
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
mfi_load="YES"
DESCRIPTION
This driver is for LSI's next generation PCI Express SAS RAID controllers. Access to RAID arrays (logical disks) from this driver is pro-
vided via /dev/mfid? device nodes. A simple management interface is also provided on a per-controller basis via the /dev/mfi? device node.
The mfi name is derived from the phrase "MegaRAID Firmware Interface", which is substantially different than the old "MegaRAID" interface and
thus requires a new driver. Older SCSI and SATA MegaRAID cards are supported by amr(4) and will not work with this driver.
Two sysctls are provided to tune the mfi driver's behavior when a request is made to remove a mounted volume. By default the driver will
disallow any requests to remove a mounted volume. If the sysctl dev.mfi.%d.delete_busy_volumes is set to 1, then the driver will allow
mounted volumes to be removed.
HARDWARE
The mfi driver supports the following hardware:
o LSI MegaRAID SAS 1078
o LSI MegaRAID SAS 8408E
o LSI MegaRAID SAS 8480E
o LSI MegaRAID SAS 9260
o Dell PERC5
o Dell PERC6
o IBM ServeRAID M5015 SAS/SATA
o IBM ServeRAID-MR10i
o Intel RAID Controller SROMBSAS18E
FILES
/dev/mfid? array/logical disk interface
/dev/mfi? management interface
DIAGNOSTICS
mfid%d: Unable to delete busy device An attempt was made to remove a mounted volume.
SEE ALSO amr(4), pci(4), mfiutil(8)HISTORY
The mfi driver first appeared in FreeBSD 6.1.
AUTHORS
The mfi driver and this manual page were written by Scott Long <scottl@FreeBSD.org>.
BUGS
The driver does not support big-endian architectures at this time.
BSD May 12, 2010 BSD