Multipathing in Solaris
Grid Infrastructure Version : 11.2.0.2
Platform : Solaris 10, Oracle Enterprise Linux 6
With reference to shared storage, I always read about MultiPathing. I know that the LUN names should appear as same across all nodes for RAC in Linux.
But 2 years back I succesfully configured RAC in Solaris 10. I left that shop and I don't have access a solaris RAC now.
If I remember correctly the LUN names appeared differently across the nodes
ie. A Particular LUN
will be seen from Node1 as:
/dev/rdsk/c3t400A0B800047D3M3210s3
The same LUN seen from Node2
/dev/rdsk/c1t400A0B800038A4CA0050s3
Although the LUN name is different, the slice number , ie the last charcter in LUN name will be same ( 3 in the above example )
Now, I am thinking , didn't this confuse the ASM Instance ? ie. For one LUN the v$asm_disk will have two entries like
v$asm_disk.path = /dev/rdsk/c3t400A0B800047D3M3210s3
v$asm_disk.path = /dev/rdsk/c1t400A0B800038A4CA0050s3
Now, I am thinking , didn't this confuse the ASM Instance ? ie. For one LUN the v$asm_disk will have two entries likemake soft link with same name and use this soft link in ASM.
Similar Messages
-
How to enable multipathing on Solaris 10
I have a Sun SPARC T2000 connected to a 2540 array.
Originally I only installed a single channel FC HBA and connected it to tray 1 of the array. Today I've installed another FC HBA and connected it to the 2nd tray of the array. When I run format on my Solaris 10 data host I can see that there are now 2 entries for the same LUN.
I've enabled multipathing by running the following command
# stmsboot -D fp -e
<reboot>
After the reboot I still see two entries for the same LUN when I run format
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c2t0d31 <SUN-UniversalXport-0670 cyl 8 alt 2 hd 64 sec 64>
/pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/ssd@w202400a0b85a1793,1f
3. c3t2d31 <SUN-UniversalXport-0670 cyl 8 alt 2 hd 64 sec 64>
/pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w202500a0b85a1793,1f
Specify disk (enter its number): ^D
I was under the impression that I should only see one entry after enabling multipathing.
Am I wrong?Further to my original posting.
I've now created a few volumes and when I run format I'm presented with the following:
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c2t0d31 <SUN-UniversalXport-0670 cyl 8 alt 2 hd 64 sec 64>
/pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/ssd@w202400a0b85a1793,1f
3. c3t2d31 <SUN-UniversalXport-0670 cyl 8 alt 2 hd 64 sec 64>
/pci@7c0/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w202500a0b85a1793,1f
4. c4t600A0B80005A0C870000027C4905FD67d0 <SUN-LCSM100_F-0670 cyl 2558 alt 2 hd 64 sec 64>
/scsi_vhci/ssd@g600a0b80005a0c870000027c4905fd67
5. c4t600A0B80005A0C870000027D4905FED3d0 <SUN-LCSM100_F-0670 cyl 51198 alt 2 hd 64 sec 64>
/scsi_vhci/ssd@g600a0b80005a0c870000027d4905fed3
6. c4t600A0B80005A0C870000027E4905FFCBd0 <SUN-LCSM100_F-0670 cyl 51198 alt 2 hd 64 sec 64>
/scsi_vhci/ssd@g600a0b80005a0c870000027e4905ffcb
7. c4t600A0B80005A1793000002A14905FF3Cd0 <SUN-LCSM100_F-0670 cyl 33278 alt 2 hd 256 sec 64>
/scsi_vhci/ssd@g600a0b80005a1793000002a14905ff3c
8. c4t600A0B80005A1793000002A34905FFEEd0 <SUN-LCSM100_F-0670 cyl 51198 alt 2 hd 64 sec 64>
/scsi_vhci/ssd@g600a0b80005a1793000002a34905ffee
9. c4t600A0B80005A17930000029E4905FCDAd0 <SUN-LCSM100_F-0670 cyl 43518 alt 2 hd 256 sec 64>
/scsi_vhci/ssd@g600a0b80005a17930000029e4905fcda
I assume the c4's are my multipath volumes, but how on earth and I going to create slices and mount them with this sort of disk alias? -
In incident # 9974 someone asked whether or not (VxVM-)DMP is supported to be used in SC3.0. The answer was no. Alternatively MPxIO shall be used.
Q1: Why is DMP disallowed to be used? I heard because of missing Persistent Reserve Support. Can someone confirm this?
Q2: Can MPxIO used generically? I was all the time under the impression that it allows only 'SUN-branded' storage to be used, therefore I considered it to be proprietary. Is this not the case (anymore)?Regarding multipathing, I have to setup a cluster with multiparthing.
The idea is to use 2 storages whic work as 'mirrored' for cluster configuration. The 2 storages will be 2 separate units (A3510FC with 1RAID controller) separated phisically ( 2 nearby buildings).
I want to have multipathing to each storage and on top of multipathing to have SDS which mirror one box to another (via metadevices).
Is this a working solution? CanI use only ufs with native multipathing from solaris? Or do I need Veritas ?
Any clue will be higly appreciated.
KR,
Mihnea -
Private Interconnect redundancy
Grid Version : 11.2.0.2
OS : Solaris 10 on HP Proliant
Currently we have a 2-node RAC running with 4 live DBs.
Currently our private interconnect is
### Current Private Interconnect
169.21.204.1 scnuprd186-privt1.mvtrs.net scnuprd186-privt1
169.21.204.4 scnuprd187-privt1.mvtrs.net scnuprd187-privt1To have redundancy for private interconnect , After repeated requests, our Unix team has finally attached a redundant NIC for each node with a redundant Gigabit-ethernet switch.
So, we need to add the below NIC to the CRS. How can we do that?
###Redundant Private Interconnect (currently attached to the server, but yet to be 'included' in the cluster)
169.21.204.2 scnuprd186-privt2.mvtrs.net scnuprd186-privt2 # Node1's newly attached redundant NIC
169.21.204.5 scnuprd187-privt2.mvtrs.net scnuprd187-privt2 # Node2's newly attached redundant NICCitizen_2 wrote:
Grid Version : 11.2.0.2
OS : Solaris 10 on HP Proliant
Currently we have a 2-node RAC running with 4 live DBs.
Currently our private interconnect is
### Current Private Interconnect
169.21.204.1 scnuprd186-privt1.mvtrs.net scnuprd186-privt1
169.21.204.4 scnuprd187-privt1.mvtrs.net scnuprd187-privt1To have redundancy for private interconnect , After repeated requests, our Unix team has finally attached a redundant NIC for each node with a redundant Gigabit-ethernet switch.You can use IPMP (IP MultiPath) in Solaris.
First, note that these should be NON-ROUTABLE addresses configured on a PRIVATE-Dedicated Switch. It would look something like this:
169.21.204.1 scnuprd186-privt1-IPMPvip.mvtrs.net scnuprd186-privt1-IPMPvip
169.21.204.2 scnuprd186-privt1-nic1.mvtrs.net scnuprd186-privt1-nic1 eth2
169.21.204.3 scnuprd186-privt1-nic2.mvtrs.net scnuprd186-privt1-nic2 eth3
169.21.204.4 scnuprd187-privt1-IPMPvip.mvtrs.net scnuprd187-privt1-IPMPvip
169.21.204.5 scnuprd187-privt1-nic1.mvtrs.net scnuprd187-privt1-nic1 eth2
169.21.204.6 scnuprd187-privt1-nic2.mvtrs.net scnuprd187-privt1-nic2 eth3
IPMP has a "real address" for each "real" interface and the IPMPvip's will "float" between the eth2 and eth3 devices depending on which one is active. Similar to the way the host vip can "float" between nodes. It is the IPMPvip addresses that are provided to the CRS configuration.
I have used this on Sun 6900's and it worked great.
Now, it can get extremely complicated if you were to also use IPMP on the public interfaces as well. It does work, you just need to pay attention to how you configure it.
>
So, we need to add the below NIC to the CRS. How can we do that?
###Redundant Private Interconnect (currently attached to the server, but yet to be 'included' in the cluster)
169.21.204.2 scnuprd186-privt2.mvtrs.net scnuprd186-privt2 # Node1's newly attached redundant NIC
169.21.204.5 scnuprd187-privt2.mvtrs.net scnuprd187-privt2 # Node2's newly attached redundant NIC -
Traffic only going through controller A on 6140
We have two seperate StorageTek 6140 arrays both with dual FC controllers and acting in a similar way, so I'm not sure if this is normal or whether its our site config.
Controller B on each array doesnt seem to be getting utilised at all when looking at the performance monitoring. It says the controller is up and our disk volumes are distributed accross both controllers as the preffered controllers. We have multipathing on Solaris 10 using traffic manager (assuming configured and working correctly).
Is this normal to only see traffic on controller A and not on controller B? I believe traffic manager is configured for round-robin load balancing but as far as I can tell this isn't what i'm seeing taking place. Where would I look to change it so the traffic load is balanced across controllers?
Forgive me, I'm new to these devices so I'm still learning how they are configured. Thanks!Hi Nik
Thanks for replying. Here is the output of a disk:
root@myhost# luxadm display /dev/rdsk/c5t600A0B800026AD9000000D3F4CA11187d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c5t600A0B800026AD9000000D3F4CA11187d0s2
Vendor: SUN
Product ID: CSM200_R
Revision: 0660
Serial Num: +(removed for privacy)+
Unformatted capacity: 102400.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x3
Maximum prefetch: 0x3
Device Type: Disk device
Path(s):
/dev/rdsk/c5t600A0B800026AD9000000D3F4CA11187d0s2
/devices/scsi_vhci/ssd@g600a0b800026ad9000000d3f4ca11187:c,raw
Controller /devices/pci@1e,600000/SUNW,qlc@3/fp@0,0
Device Address 200600a0b8290184,bb
Host controller port WWN 210000e08b921406
Class secondary
State STANDBY
Controller /devices/pci@1e,600000/SUNW,qlc@2/fp@0,0
Device Address 200700a0b8290184,bb
Host controller port WWN 210000e08b924106
Class primary
State ONLINE
After learning some more about how the 6140 works (I believe it is called an asymmetric array, at any one time a single volume will be owned by one controller, and all I/O to that volume will be via the path to that controller and not via round-robin), I believe it to be a software/firmware bug.
We have no problems communicating to volumes on preferred controller B and there are no alarms, so i can only conclude trafic must be going through that controller. But a volume on controller B will have no performance stats showing in CAM unless it is moved to controller A (stats subsequently go away again when moved back to controller B). Its not affecting the operation of the array, we just can't get volume performance stats on anything using controller B :(
CAM is 6.6 and IOM is 98D0 (latest is 98D3). -
StorageTek 6140 / CAM 6.1 newby, setup Qs
Just got a M4000 with a 6140 connected via dual Fibre HBA. Confused what S/W is installed where. I installed the CAM s/w on the M4000 (Data Host?) but I just re-read a StorageTek Array Admin Gde that says the management s/w (CAM?) must be installed on a Sun workstation - .i.e. not on my M4000 is this true? A 2nd Sun system needs to be used to run the CAM application?
Lastly, if M4000 is running Solaris 10 is there any Data Host s/w (drivers, etc.) that I have to install or is it already included in pre-installed Solaris 10 O/S on my M4000 or do I have to find a Solaris 10 O/S CD that has extra array drivers that I need to install? I did enable Multipathing on Solaris 10 via the stmsboot.
Any guidance is greatly appreciated.
DeanFYI - I answered my own Qs with a bunch of RTFM and trial-and-error.
I originally put the CAM S/W on the M4000 (is data host). Obtained a static IP # for network connection to 6140 Controller A and used laptop to connect to 6140 via seria cable (with proper serial-to-CAT-5 adaptor) to configure IP for controller. Then I could go to URL CAM S/W Install Gde said to use from my desktop and Register 6140 by supplying IP instead of searching network. Was able to register 6140 but network guys complained of "flapping" between M4000 and 6140 so I uninstallled CAM on M4000 and installed it on spare Ultra 25, re-registerd 6140 but network guys say I'm still "flapping".
As for S/W on M4000 to drive 6140 array - Solaris 10 includeds necessary drivers and no need to download SAN S/W from Sun. I did issue Solaris command to support Multipathing.
As for configuring the 6140 with 6-146GB,15KRPM FC-AL disks: I don't have any Premium Licenses as this M4000 will be the only data host to use the 6140... I have a Oracle 10 D/B to house on 6140 so starting with adding a storage pool that asks for a storage profile - I chose ORACLE_OLTP_HA. Then I created a Volume referencing the added storage pool so when I select all 6 disks I got Raid 1+0 and half the total disk space of the 6 disks. I finally created an initiator - the only unkown was when it wanted Unique Identifier (WWN) the Volume create screens listed a WWN of 32chars (WWN of 1st and 6th disk in my volume) but Create Initiator screen wouldn't take this - just had to give it the WWN of 1st disk of Volume and then used hostname of M4000 as only host associated with this initiator.
After a quick reboot of M4000 format finally saw a big 400GB+ disk!!!! The format tool showed the same 8 slices to configure as with individual disks. I zeroed-out all slices but slice 0 and mapped the entire Volume to this slice.
Now for a follow-up Q:
I got this big disk on the array created but I need more than 7 slices to carve it up. What's the best way to do it? A guy here that has older disk arrays has always used Volume Mgr S/W and created 1 big Concat over the entire array volume and chopped it up via soft partitions. Is this a good approach that will achieve good performance? Is there a way to chop up the disks within CAM so M4000 sees multiple logical disks that I can then use the 7 slices per each logical disk for my mount pts? I want to keep Raid 1+0 if possible.
Dean U. -
Recommendations for Multipathing software in Sun Cluster 3.2 + Solaris 10
Hi all, I'm in the process of building a 2-node cluster with the following specs:
2 x X4600
Solaris 10 x86
Sun Cluster 3.2
Shared storage provided by a EMC CX380 SAN
My question is this: what multipathing software should I use? The in-built Solaris 10 multipathing software or EMC's powerpath?
Thanks in advance,
StewartHi,
according to http://www.sun.com/software/cluster/osp/emc_clarion_interop.xml you can use both.
So at the end it all boils down to
- cost: Solaris multipathing is free, as it is bundled
- support: Sun can offer better support for the Sun software
You can try to browse this forum to see what others have experienced with Powerpath. From a pure "use as much integrated software as possible" I would go with the Solaris drivers.
Hartmut -
Solaris 10 - native cluster, multipath, volume management.
Hi,
I have downloaded Solaris 10 x86 DVD. Planning to install it inside VMWare. Kindly let me know if there is any native clustering , multipathing and volume management software thats pre bundled with Solaris 10 or is it paid?
I am a storage admin and I want to get a clear understanding of how the above mentioned things work. Will install two instances of Solaris 10 and try out a couple of things.
Please let me know.Hi Pascal,
Thank you for such a quick reply.
I am looking for a clustering software that will basically be free, yet give me a glimpse of how the clustering stuff works on Solaris. I cannot afford the paid stuff, so will have to make do with the freebies...If my understanding is correct, you are stating that the native multipathing and volume management is integrated AND free. Kindly let me know.
So if I install a few virtual disks inside VMware, can I use the native multipathing to detect them? I cant get the vmware solaris to access SAN, so basically looking for something that will make the OS "think" that its getting SAN LUNs, so that I can try multipathing.
Sorry for topping up another question.
Edited by: 992432 on Mar 7, 2013 3:40 AM -
Solaris 10 Storage multipathing virtual devices
Hi all,
In Solaris 10, after enabling the storage multi-pathing using "stmsboot -e", the newly created virtual devices with long names containing the WWW. Is it possible to rename those device names? Actualy, in the Oracle 10g RAC, it is required that the two nodes see the same device names for the shared storage, so is it possible to rename the multi-path devices?
If not, then is it possible to create links to those devices so that the links them selfs wil be used in the Oracle setup? would it be safe to use the regular hard links? or is it possible to create a new device file pointing to the multi-path device and have this device file name the same on both RAC nodes?
BestAny ideas?
-
Solaris 8 IP Multipathing ping rate
Hi:
Has anyone characterized the relationship between the vaule of FAILURE_DETECTION_TIME
in /etc/default/mpathd and the rate at which the test IP addresses will be pinged.
From an initial snoop with FAILURE_DETECTION_TIME=10000 (defalut of 10 seconds)
it looks like the pings occur every second or so.
thanksIt's variable to not induce pathological behaviour.
-
How to Install Multipath Raw Device for Voting/OCR IN RHEL5 U1
Dear all,
Setup
Two Node RAC Cluster with IBM disk Array DS4700
OS- RHEL 5 Update1 (2.6.18-53.el5)
Oracle- 10.2.0.1
Failover Driver- RDAC Driver (Linux MPP Driver Version: 09.02.C5.16)
I am trying to follow Metalink Note-564580.1
But when i am configuring Multipathing and Verify Multipath Devices.
I am not getting any output when i am issuing the following command
#multipath -ll
I checked the service mulipath
[root@db1 dev]# service multipathd status
multipathd (pid 3845) is running...
[root@db1 dev]#
Please let me know, if you have solution.
Rgds
Sumit
Bangalore,India[root@wmcdb2 ~]# service multipathd restart
Stopping multipathd daemon: [ OK ]
Starting multipathd daemon: [ OK ]
[root@wmcdb2 ~]#
==========================================================
==========================================================
[root@wmcdb2 ~]# fdisk -l
Disk /dev/sda: 146.5 GB, 146578341888 bytes
255 heads, 63 sectors/track, 17820 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 131 1052226 83 Linux
/dev/sda2 132 7143 56323890 83 Linux
/dev/sda3 7144 8187 8385930 82 Linux swap / Solaris
/dev/sda4 8188 17820 77377072+ 5 Extended
/dev/sda5 8188 17820 77377041 83 Linux
Disk /dev/sdb: 2147 MB, 2147483648 bytes
67 heads, 62 sectors/track, 1009 cylinders
Units = cylinders of 4154 * 512 = 2126848 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 1009 2095662 83 Linux
Disk /dev/sdc: 1073 MB, 1073741824 bytes
34 heads, 61 sectors/track, 1011 cylinders
Units = cylinders of 2074 * 512 = 1061888 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 1011 1048376+ 83 Linux
Disk /dev/sdd: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sde: 108.0 GB, 108005425152 bytes
255 heads, 63 sectors/track, 13130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sde doesn't contain a valid partition table
Disk /dev/sdf: 48.3 GB, 48318382080 bytes
64 heads, 32 sectors/track, 46080 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/sdf doesn't contain a valid partition table
Disk /dev/sdg: 24.5 GB, 24551358464 bytes
64 heads, 32 sectors/track, 23414 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/sdg doesn't contain a valid partition table
===============================================
===============================================
[root@wmcdb2 ~]# multipath -ll
mpath2 (3600a0b80002ab33400000893489f7c76) dm-2 IBM,VirtualDisk
[size=100G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:3 sdd 8:48 [active][ready]
mpath1 (3600a0b8000501e1600000897489f7f52) dm-1 IBM,VirtualDisk
[size=1.0G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:2 sdc 8:32 [active][ready]
mpath0 (3600a0b80002ab33400000890489f7c34) dm-0 IBM,VirtualDisk
[size=2.0G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:1 sdb 8:16 [active][ready]
mpath5 (3600a0b8000501e160000089b489f7fd2) dm-5 IBM,VirtualDisk
[size=23G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:6 sdg 8:96 [active][ready]
mpath4 (3600a0b80002ab33400000895489f7cb9) dm-4 IBM,VirtualDisk
[size=45G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:5 sdf 8:80 [active][ready]
mpath3 (3600a0b8000501e1600000899489f7f7f) dm-3 IBM,VirtualDisk
[size=101G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:4 sde 8:64 [active][ready]
[root@wmcdb2 ~]#
=====================================================
=====================================================
[root@wmcdb2 ~]# cat /proc/partitions
major minor #blocks name
8 0 143142912 sda
8 1 1052226 sda1
8 2 56323890 sda2
8 3 8385930 sda3
8 4 1 sda4
8 5 77377041 sda5
8 16 2097152 sdb
8 17 2095662 sdb1
8 32 1048576 sdc
8 33 1048376 sdc1
8 48 104857600 sdd
8 64 105474048 sde
8 80 47185920 sdf
8 96 23975936 sdg
=============================================
============================================
[root@wmcdb2 ~]# cat /etc/multipath.conf
defaults {
user_friendly_names yes
defaults {
udev_dir /dev
polling_interval 10
selector "round-robin 0"
path_grouping_policy failover
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout /bin/true
path_checker readsector0
rr_min_io 100
rr_weight priorities
failback immediate
# no_path_retry fail
user_friendly_name yes
devnode_blacklist {
&n sp; devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
d vnode "^hd[a-z]"
devnode "^sda"
nbsp; devnode "^cciss!c[0-9]d[0-9]*"
multipaths {
nbsp; multipath {
& bsp; wwid 3600a0b80002ab33400000890489f7c34
alias ocr1
multipath {
wwid 3600a0b8000501e1600000897489f7f52
alias voting1
[root@wmcdb2 ~]#
=================================================== -
[SOLVED] multipath-tools build fails because file is not a directory
Hi all,
I'm trying to build the multipath-tools-git AUR package (I'm playing around with virtualization, and need the kpartx tool). I tried building, and got this output:
(NOTE: /home/gregory/AUR PACKAGES is symlinked to /mnt/STORAGE/AUR PACKAGES, which shows up in this build. I tried building without using the symlink, and it didn't change anything.)
[gregory@whitcomb multipath-tools-git]$ makepkg -s
==> Making package: multipath-tools-git 1295.81895af-1 (Sat Sep 7 16:50:52 EDT 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating multipath-tools-git git repo...
Fetching origin
==> Validating source files with md5sums...
multipath-tools-git ... Skipped
==> Extracting sources...
-> Creating working copy of git repo...
Cloning into 'multipath-tools-git'...
done.
==> Starting pkgver()...
==> Starting prepare()...
==> Removing existing pkg/ directory...
==> Starting build()...
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o memory.o memory.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o parser.o parser.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o vector.o vector.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o devmapper.o devmapper.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o callout.o callout.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o hwtable.o hwtable.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o blacklist.o blacklist.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o util.o util.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o dmparser.o dmparser.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o config.o config.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o structs.o structs.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o discovery.o discovery.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o propsel.o propsel.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o dict.o dict.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o pgpolicies.o pgpolicies.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o debug.o debug.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o regex.o regex.c
regex.c: In function ‘re_match_2’:
regex.c:3297:17: warning: variable ‘sdummy’ set but not used [-Wunused-but-set-variable]
const char *sdummy;
^
regex.c:3296:20: warning: variable ‘pdummy’ set but not used [-Wunused-but-set-variable]
unsigned char *pdummy;
^
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o defaults.o defaults.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o uevent.o uevent.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o switchgroup.o switchgroup.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o uxsock.o uxsock.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o print.o print.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o alias.o alias.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o log_pthread.o log_pthread.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o log.o log.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o configure.o configure.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o structs_vec.o structs_vec.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o sysfs.o sysfs.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o prio.o prio.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o checkers.o checkers.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o lock.o lock.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o waiter.o waiter.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o file.o file.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o wwids.o wwids.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -c -o prioritizers/alua_rtpg.o prioritizers/alua_rtpg.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -Wl,-soname=libmultipath.so.0 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -DLIBDM_API_FLUSH -D_GNU_SOURCE -DLIBDM_API_COOKIE -o libmultipath.so.0 memory.o parser.o vector.o devmapper.o callout.o hwtable.o blacklist.o util.o dmparser.o config.o structs.o discovery.o propsel.o dict.o pgpolicies.o debug.o regex.o defaults.o uevent.o switchgroup.o uxsock.o print.o alias.o log_pthread.o log.o configure.o structs_vec.o sysfs.o prio.o checkers.o lock.o waiter.o file.o wwids.o prioritizers/alua_rtpg.o -lpthread -ldl -ldevmapper -ludev
ln -sf libmultipath.so.0 libmultipath.so
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath/prioritizers'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o random.o random.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libpriorandom.so random.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o const.o const.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libprioconst.so const.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o hp_sw.o hp_sw.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libpriohp_sw.so hp_sw.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o emc.o emc.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libprioemc.so emc.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o rdac.o rdac.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libpriordac.so rdac.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o alua.o alua.c
alua.c: In function ‘get_alua_info’:
alua.c:58:6: warning: variable ‘aas’ set but not used [-Wunused-but-set-variable]
int aas;
^
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libprioalua.so alua.o alua_rtpg.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o ontap.o ontap.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libprioontap.so ontap.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o datacore.o datacore.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libpriodatacore.so datacore.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o hds.o hds.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libpriohds.so hds.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o weightedpath.o weightedpath.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libprioweightedpath.so weightedpath.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o iet.o iet.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libprioiet.so iet.o
rm random.o weightedpath.o ontap.o hp_sw.o hds.o rdac.o const.o datacore.o emc.o iet.o
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath/prioritizers'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath/checkers'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o libsg.o libsg.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o cciss_tur.o cciss_tur.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libcheckcciss_tur.so libsg.o cciss_tur.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o readsector0.o readsector0.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libcheckreadsector0.so libsg.o readsector0.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o tur.o tur.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libchecktur.so libsg.o tur.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o directio.o directio.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libcheckdirectio.so libsg.o directio.o -laio
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o emc_clariion.o emc_clariion.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libcheckemc_clariion.so libsg.o emc_clariion.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o hp_sw.o hp_sw.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libcheckhp_sw.so libsg.o hp_sw.o
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I.. -c -o rdac.o rdac.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro -shared -o libcheckrdac.so libsg.o rdac.o
rm tur.o hp_sw.o rdac.o readsector0.o cciss_tur.o emc_clariion.o
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath/checkers'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmpathpersist'
cc -Wall -fPIC -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist *.c
cc -shared -lpthread -ldevmapper -ldl -L../libmultipath -lmultipath -Wl,-soname=libmpathpersist.so.0 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -o libmpathpersist.so.0 mpath_persist.o mpath_updatepr.o mpath_pr_ioctl.o
ln -s libmpathpersist.so.0 libmpathpersist.so
/usr/bin/gzip -9 -c mpath_persistent_reserve_in.3 > mpath_persistent_reserve_in.3.gz
/usr/bin/gzip -9 -c mpath_persistent_reserve_out.3 > mpath_persistent_reserve_out.3.gz
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmpathpersist'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/multipath'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -c -o main.o main.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath main.o -o multipath -Wl,-O1,--sort-common,--as-needed,-z,relro -lpthread -ldevmapper -ldl -L../libmultipath -lmultipath -ludev
/usr/bin/gzip -9 -c multipath.8 > multipath.8.gz
/usr/bin/gzip -9 -c multipath.conf.5 > multipath.conf.5.gz
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/multipath'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/multipathd'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o main.o main.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o pidfile.o pidfile.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o uxlsnr.o uxlsnr.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o uxclnt.o uxclnt.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o cli.o cli.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o cli_handlers.o cli_handlers.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist main.o pidfile.o uxlsnr.o uxclnt.o cli.o cli_handlers.o -Wl,-O1,--sort-common,--as-needed,-z,relro -lpthread -ldevmapper -lreadline -ludev -ldl -L../libmultipath -lmultipath -L../libmpathpersist -lmpathpersist -o multipathd
/usr/bin/gzip -9 -c multipathd.8 > multipathd.8.gz
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/multipathd'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/mpathpersist'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist -c -o main.o main.c
cc -g main.o -o mpathpersist -Wl,-O1,--sort-common,--as-needed,-z,relro -lpthread -ldevmapper -L../libmpathpersist -lmpathpersist -L../libmultipath -lmultipath -ludev -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I../libmultipath -I../libmpathpersist
/usr/bin/gzip -9 -c mpathpersist.8 > mpathpersist.8.gz
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/mpathpersist'
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/kpartx'
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o bsd.o bsd.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o dos.o dos.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o kpartx.o kpartx.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o solaris.o solaris.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o unixware.o unixware.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o dasd.o dasd.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o sun.o sun.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o gpt.o gpt.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o mac.o mac.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o ps3.o ps3.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o crc32.o crc32.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o lopart.o lopart.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o xstrncpy.o xstrncpy.c
cc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\"usr/lib64\" -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLIBDM_API_COOKIE -c -o devmapper.o devmapper.c
cc bsd.o dos.o kpartx.o solaris.o unixware.o dasd.o sun.o gpt.o mac.o ps3.o crc32.o lopart.o xstrncpy.o devmapper.o -o kpartx -ldevmapper
/usr/bin/gzip -9 -c kpartx.8 > kpartx.8.gz
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/kpartx'
==> Entering fakeroot environment...
==> Starting package()...
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath'
install -d /home/gregory/AUR packages/multipath-tools-git/pkg/multipath-tools-git//usr/lib
install -m 755 libmultipath.so.0 /home/gregory/AUR packages/multipath-tools-git/pkg/multipath-tools-git//usr/lib/libmultipath.so.0
install: target ‘packages/multipath-tools-git/pkg/multipath-tools-git//usr/lib/libmultipath.so.0’ is not a directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath'
make: *** [recurse_install] Error 2
==> ERROR: A failure occurred in package().
Aborting...
[gregory@whitcomb multipath-tools-git]$
I noticed there was a typo from the line:
install: target ‘packages/multipath-tools-git/pkg/multipath-tools-git//usr/lib/libmultipath.so.0’ is not a directory
with the duplicated slash, so I edited the package() section of the PKGBUILD to remove the duplicated slash
make LIB="/usr/lib" DESTDIR="${pkgdir}" install
to
make LIB="usr/lib" DESTDIR="${pkgdir}" install
However, rebuilding the package caused the same error to occur (only relevant part shown)
==> Starting package()...
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath'
install -d /home/gregory/AUR packages/multipath-tools-git/pkg/multipath-tools-git/usr/lib
install -m 755 libmultipath.so.0 /home/gregory/AUR packages/multipath-tools-git/pkg/multipath-tools-git/usr/lib/libmultipath.so.0
install: target ‘packages/multipath-tools-git/pkg/multipath-tools-git/usr/lib/libmultipath.so.0’ is not a directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools-git/src/multipath-tools-git/libmultipath'
make: *** [recurse_install] Error 2
==> ERROR: A failure occurred in package().
Aborting...
So that couldn't have been the problem. There doesn't seem to be any indication on the AUR page that someone else ran into this problem. I also checked the upstream site as well as the mailing lists, and didn't see anything resembling my problem.
Just to make sure that I hadn't downloaded some bad build from git, I also tried installing the multipath-tools package from the AUR, since that should have at least worked for the packager. However, I got the exact same (albeit sooner cause it didn't have to download git sources):
==> Starting package()...
make[1]: Entering directory `/mnt/STORAGE/AUR packages/multipath-tools/src/libmultipath'
install -d /mnt/STORAGE/AUR packages/multipath-tools/pkg/multipath-tools/usr/lib
install -m 755 libmultipath.so.0 /mnt/STORAGE/AUR packages/multipath-tools/pkg/multipath-tools/usr/lib/libmultipath.so.0
install: target ‘packages/multipath-tools/pkg/multipath-tools/usr/lib/libmultipath.so.0’ is not a directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/mnt/STORAGE/AUR packages/multipath-tools/src/libmultipath'
make: *** [recurse_install] Error 2
==> ERROR: A failure occurred in package().
Aborting...
I'm guessing there's probably some configuration issue with my machine causing this problem, but I have no idea where it would come from. If anybody else has any other ideas on how to proceed, I'd be really appreciative. And if any more information is needed, let me know! Thanks!
Last edited by cactaur (2013-09-08 05:23:36)Of course, soon after I post this, I stumble upon the solution. It turns out that having a path with a space in it can cause certain packages to bug out while building. I changed the "AUR Packages" folder to "AUR-packages", and then it built successfully. Guess that's something to look out for.
-
Question about SMC agent port binding on a system with IP multipathing
Hi All, I hope this is the correct forum
I have recently upgraded a server to from Solaris 8 to Solaris 9 and SMC version 3 to version 3.5 update1 and have been able to configure the agent to bind to the loopback interface.
Originally on the Solaris 8 system with IP multipathing and SMC version 3 we had the following configuration in the domain-config.x file, and when agent was started it would bind to the localhost:
agent = {
snmpPort = "20161"
lsof output:
esd 804 root 10u IPv4 0x30002e233d0 0t0 UDP *:20161 (Idle)
Now since the upgrade of the server and installation of SMC we are seeing that the agent now binds to all the IP address configured on the server, I have tried setting the �agentServer� to localhost or 127.0.0.1 but SMC agent will not start. Also have tried changing/removing the logicalAddressMode setting but with no luck agent still binds to all IP address.
lsof output:
esd 267 root 10u IPv4 0x300073afcb8 0t0 UDP hostname-eri0:20161 (Idle)
esd 267 root 11u IPv4 0x30003d30968 0t0 UDP hostname:20161 (Idle)
esd 267 root 12u IPv4 0x300073364a8 0t0 UDP hostname-eri1:20161 (Idle)
agent = {
agentServer = "hostname"
logicalAddressMode = "ip"
snmpPort = "20161"
I have tried finding documentation on the domain-config.x file but have only found references to existing examples not a document covering all the possible varibles and what they mean.
Thanks for any assistanceI got an idea:
In the Subscriber Profile, in the "messages" section. You can try and add:
- where it says "x" use the actual extension of the the subscriber mailbox + the MWI code. 5555*72
Just to see if it turns it on..... maybe?? Otherwise I don't know if Unity is going to be able to distinguish what is a Cisco phone and what is an Avaya phone. The UTIM is the piece that is supposed to seperate the two systems. But what you are doing is joining them together via the CCM. Which you have working, but MWI is going to be tricky.
This is where the PBXlink would come in handy. You would install this onto the Unity box. Then change your Avaya subscriber from CCM integration to the PBXlink integration. Calls can still come in from CCM, but MWI signals will go out the PBXlink.
If you notice in the Subscriber profile, you can assign subscribers to different Integrations. This plays a huge part in MWI. I think what you are trying is a great stab at it... but I think you may be chasing your tail on this one with the MWI.
On the CallManager side, what happens when you dial an Avaya phone? Do you have a route or translation pattern setup? Because if there was a way to translate this example:
ext 4455 gets a new voicemail
Unity dials 4455 to CCM with MWI on code xxxx
CCM would translate and route this pattern as 4455 *72 to the Avaya switch. Avaya switch should turn on the light.
So basically, CCM is pushing the 4455 through the CAS T1, then add *72 to it as a translation from 4455 xxxx (xxxx being your callmanager MWI on code)
It's a stab in the dark... but that's the only, if it would work I can think off without the PBXlink.
good luck! -
Solaris 11.1 Comstar FC target
Hello,
I have a problem with the comstar as a FC target.
New install of Solaris 11.1
HBA is an Emulex LPe11002
Brocade 5100B switches
2x 10x 3TB NL-SAS disks in raidz2 in pool
It all works, but the speed is unusable slow to the LUN.
iSCSI work and I am able to hit the max of the network so there is no problems with access to access the disks.
HBA info
HBA Port WWN: 10000000c98e9712
Port Mode: Target
Port ID: 12000
OS Device Name: Not Applicable
Manufacturer: Emulex
Model: LPe11002-E
Firmware Version: 2.80a4 (Z3F2.80A4)
FCode/BIOS Version: none
Serial Number: VM92923844
Driver Name: emlxs
Driver Version: 2.70i (2012.02.10.12.00)
Type: F-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c98e9712
HBA Port WWN: 10000000c98e9713
Port Mode: Target
Port ID: 22000
OS Device Name: Not Applicable
Manufacturer: Emulex
Model: LPe11002-E
Firmware Version: 2.80a4 (Z3F2.80A4)
FCode/BIOS Version: none
Serial Number: VM92923844
Driver Name: emlxs
Driver Version: 2.70i (2012.02.10.12.00)
Type: F-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c98e9713
iostat 2 sec apart:
pool alloc free read write read write
dipool 44.1M 54.5T 0 19 1.01K 134K
dipool 44.1M 54.5T 0 2 0 196K
dipool 45.0M 54.5T 0 50 0 210K
dipool 45.0M 54.5T 0 0 0 64.0K
dipool 45.8M 54.5T 0 50 0 274K
dipool 45.8M 54.5T 0 0 0 64.0K
dipool 45.8M 54.5T 0 0 0 0
dipool 45.0M 54.5T 0 35 0 125K
dipool 45.0M 54.5T 0 0 0 64.0K
dipool 44.5M 54.5T 0 34 0 61.0K
dipool 44.5M 54.5T 0 0 0 64.0K
dipool 44.5M 54.5T 0 0 0 64.0K
dipool 44.6M 54.5T 0 34 0 61.0K
dipool 44.6M 54.5T 0 0 0 64.0K
I also tried openindiana, the speed was good, but link will die and then capturing stmf debug shows the following when using the Emulex.
FROM STMF:210406652: abort_task_offline called for LPORT: lport abort timed out, 1000's of them
Jun 7 14:02:18 emlxs: [ID 349649 kern.info] [ 5.0608]emlxs1: NOTICE: 730: Link reset. (Disabling link...)
Jun 7 14:02:18 emlxs: [ID 349649 kern.info] [ 5.0333]emlxs1: NOTICE: 710: Link down.
Jun 7 14:04:41 emlxs: [ID 349649 kern.info] [ 5.055D]emlxs1: NOTICE: 720: Link up. (4Gb, fabric, target)
Jun 7 14:04:41 fct: [ID 132490 kern.notice] NOTICE: emlxs1 LINK UP, portid 22000, topology Fabric Pt-to-Pt,speed 4G
Jun 7 14:10:19 emlxs: [ID 349649 kern.info] [ 5.0608]emlxs1: NOTICE: 730: Link reset. (Disabling link...)
Jun 7 14:10:19 emlxs: [ID 349649 kern.info] [ 5.0333]emlxs1: NOTICE: 710: Link down.
Jun 7 14:12:40 emlxs: [ID 349649 kern.info] [ 5.055D]emlxs1: NOTICE: 720: Link up. (4Gb, fabric, target)
Jun 7 14:12:40 fct: [ID 132490 kern.notice] NOTICE: emlxs1 LINK UP, portid 22000, topology Fabric Pt-to-Pt,speed 4G
I also tried a Qlogic QLE2460-SUN and that has the same problem in both OI and Solaris, ultra slow
HBA Port WWN: 2100001b3280b
Port Mode: Target
Port ID: 12000
OS Device Name: Not Applicable
Manufacturer: QLogic Corp.
Model: QLE2460
Firmware Version: 5.2.1
FCode/BIOS Version: N/A
Serial Number: not available
Driver Name: COMSTAR QLT
Driver Version: 20100505-1.05
Type: F-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 2000001b3280b
It seems no one is using Solaris as a FC target anymore and since we do not have 10Gbe in our lab and some systems cannot communicate via IP to others, FC is the only form of backup.
Can someone please let me know if they are using Solaris as an FC target and perhaps some pointers. On the example above I am trying to clone using VMware from a LUN on an EMC array to the Solaris node. As I mentions the speed is good in OI, but then it seems there is a driver issue.
Cloning in OI from the EMC LUN to the back server:
1 sec apart.
alloc free read write read write
>>>>>>> ----- ----- ----- ----- ----- -----
>>>>>>> 309G 54.2T 81 48 452K 1.34M
>>>>>>> 309G 54.2T 0 8.17K 0 258M
>>>>>>> 310G 54.2T 0 16.3K 0 510M
>>>>>>> 310G 54.2T 0 0 0 0
>>>>>>> 310G 54.2T 0 0 0 0
>>>>>>> 310G 54.2T 0 0 0 0
>>>>>>> 310G 54.2T 0 10.1K 0 320M
>>>>>>> 311G 54.2T 0 26.1K 0 820M
>>>>>>> 311G 54.2T 0 0 0 0
>>>>>>> 311G 54.2T 0 0 0 0
>>>>>>> 311G 54.2T 0 0 0 0
>>>>>>> 311G 54.2T 0 10.6K 0 333M
>>>>>>> 313G 54.2T 0 27.4K 0 860M
>>>>>>> 313G 54.2T 0 0 0 0
>>>>>>> 313G 54.2T 0 0 0 0
>>>>>>> 313G 54.2T 0 0 0 0
>>>>>>> 313G 54.2T 0 9.69K 0 305M
>>>>>>> 314G 54.2T 0 10.8K 0 337M
We have tons of other devices connected to the Brocade 5100B switches. I tried connecting the system to two different switches individually with the same result. We are basically 100% Emulex shop and I only have the one qlt card
I have now tried a brand new Emulex LPe11002 card in a different PCI-E slot, new cable and different FC switch.
I have similar problems with Openindiana and no problems with any of the emc vnx/cx/data domain connected to the same switches or any of the hosts connected to them as the targets using the same LPe10000/LPe11002/LPe12002 cards.
Any help/pointers would be greatly appreciated.
Thanks,Accidentally found this. Some comments. Unfortuinately, we run Solaris FC as initiators/clients to san target LUNs on NetApp and HP.
1. There were patches in sol 10 for fc cards for bugs, driver and firmware upgrades, fcode/bios which I believe is for san boot only.
I read somewhere these patches for sun/oracle branded FC cards would not be released under Sol 11, have not looked.
Sample patches for Qlogic for Sol 10 are 114874-07 for fcode/bios and 149175-03 for everything else. Unfortunately we're most Qlogic and only have a couple Emulex in Linux systems. So is 11.1 really supporting these FC cards now or is the user responsible for downloading drivers and firmware from vendors and installing?.
2. Have heard when zfs gets to around 80% capacity i/o performance can suffer. This may have been fixed, been avoiding with quotas.
Then of course if looking for continuous speed don't turn on compression.
3. Do you have/need the sol 11.1 multi-path package when Solaris has the targets/LUNs? Are you configured for MPxIO?
pkg info system/storage/multipath-utilities
4. Do you need any kernel changes to /etc/system for performance? Some below are x86.
set sd:sd_max_throttle=64 sparc
set ssd:ssd_max_throttle=64 x86
set maxphys=1048576
set ssd:ssd_io_time=60 x86
5. Do you need to worry about 4K alignment from client side?
These are all things I worry about but Solaris is an initiator in our environment along with every other platform.
This is old and hopefully resolved by this time!
where (s)sd_max_throttle= 256
/ # of LUNs -
Solaris 10 can not boot; disks drive offline
hi, solaris 10 can not boot the operating system has 10 luns and this enabled the multipathing, he settled patches and reboot the computer does not start showing me the following errors:
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1f (ssd0): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1e (ssd3): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1d (ssd5): drive offline
into failsafe mode and slow 2 days in, I try to see the running operating system disk format and takes the response format and shows me the following errors:
# format
Searching for disks...WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1f (ssd0): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1e (ssd3): drive offline
WARNING: /pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875837d,1d (ssd5): drive offline
hba ports have been connected
# luxadm -e port
/devices/pci@0/pci@0/pci@8/pci@0/pci@1/SUNW,qlc@0/fp@0,0:devctl CONNECTED
/devices/pci@0/pci@0/pci@8/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl CONNECTED
# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c2 fc-fabric connected configured unknown
c2::203400a0b875837d disk connected configured unknown
c3 fc-fabric connected configured unknown
c3::202400a0b875837d disk connected configured unknown
cfgadm -al command output c2 and c3 appears has been connected and configured, because luns in the format output informs me that disks have state drive offline?
any idea.Hi--
Can you list the steps that lead this problem, please?
The drive offline message is a symptom of some kind of connection or underlying hardware problem.
If there were no system changes that lead to this problem, then I would look for connection or hardware issues.
Thanks, Cindy
Maybe you are looking for
-
How to Clear "recent" listing in new Acrobat X Pro
In new Acrobat X Pro, when I open this program a window appears listing "recent" files that I have previously opened. I cannot clear this "recent" listing. I have deleted some of those files, and do not want them to appear in this window anymore. I c
-
Display blob field on pdf with pl_fpdf
Hi All, I wish I could use some method to output PDF from the PL/SQL. I already have a document (image stored as BLOB). Now, I need to output this image in PDF. I know doing this outside database is easy and advisable. When I use pl_fpdf with image f
-
Macbook freezing when restarting to update
I'm trying to update my 2010 Macbook Pro to the newest OS + itunes versions, but it freezes when restarting (it's showing the space screen indefinitely). Anyone has a solution, I can try? Many thanks
-
The MBA mid 2011 is connected to the new thumderbolt display. If I want to use the MBA all by itself, and disconnect it from the Thunderbolt display, can I simply leave the TB display powered on or should I turn the power off? Which way is it better
-
I have an iMac that I purchased back in 2010 and over the past 9 month or less my computer just started shutting down while someone was in the process or working on it. What could this come from? Is there a simple solutions to this problem?