OVS Storage

Hello guys !!!
My question : is it possible to use local (raw) hard disk as storage and how to ?
Is there a modification or TR needed ?
I already read the doc , it said it is recognize automatically , but it is not for me
Here is my confg for my server : 3 hard disks
1 hard disk : where the system is
2nd hard disk : for backup and keep doc
3rd hard disk : added as raw disk to be the local storage but still it is not recognized
Any ideas ?

hi
i had the similar issue (i think u r talking about 3.0.2 or 3.0.3).
for local storage u hav to put ur storage hard disk on the vmserver machine
ie- 1 hard disk- vm server
2 hard disk - local storage
what u hav to do....
dont create any partition on storage hardisk and dont format also
from the command line of vm server just delete the storage hard disk
ie - fdisk -l ( to get a listing of your current partition )
fdisk /dev/hdb (i am assuming hdb as ur storage hard disk )
Command (m for help): p ( to list all the partitioning of that disk)
Command (m for help): d (to delete the partition)
Partition number (1-2): 1
and just save and exit...after that dont do any thing just restart ur system
now go to vm manager this will come automatically
may be this will help u !
Thanks
Abhishek Anand

Similar Messages

  • Oracle VM 3.2.1 test setup - problems with OVS node evictions

    Hi all
    I am building a small test environment for Oracle VM with the following configuration
    4 boxes, each 1 x AMD 6 core cpu + 32GB RAM + 2 x 1GB ethernet (10.30.32.n, 192.168.20.n networks - I only have 1x16 port GB switch, so all cabling is through the one switch - that may be part of the problem)
    3 boxes are diskless, running Oracle VM Server from 8GB USB flash drive
    1 Box is EL6.3 and set up with:
    1x750GB with (LVM) partitions for /, /u01 (Oracle 11gR2SE + OVM Manager), swap, and a partition for the OVS pool
    4x2TB drives, set up with LVM striping, and 4 LVs - 1 750GB for virtualbox and VMWare VMs, and 3 others for OVS storage repositories (each a bit over 2TB) - all ext4.
    The OVS Pool and OVS Storage file systems are exported via NFS
    VM server and VM manager installs all went smoothly. Servers and storage are discovered OK in the manager.
    I created 2 networks - one on the 10.30.32 subnet for Server Management, Cluster Heartbeat and Live Migrate (also the public network for accessing the machines). The other on the 192.168.20 subnet for Storage and Virtual Machine.
    Created storage pools, and presented to all the servers.
    In creating the Server Pool, just took the default 120 for the cluster timeout
    Now when I try to import an assembly, or a VM template, it gets so far, then then the server doing the actual job reboots.
    My initial thought is that for whatever reason the NFS traffic involved in importing and writing - either network, or I/O on the NFS server - is swamping the cluster heartbeat traffic, and the node just fences itself
    Just wondering if anyone has any ideas or suggestions, or can advise what further diagnostics or troubleshooting I can do

    I suspect it more to do with your storage than anything. Run your import again and sample your I/O performance from your NFS server during the import. Also, if you can... .create LACP bond on your NFS server. I don't know what kind of throughput you expect but remember. A single GB nic can only do a max of 125/MB a sec. That sounds rather good but take into consideration everything you're doing across your environment... its not a lot. I see well over 400 mb/sec network throughput at times on my storage. I run bonded 10GB nics.
    Once you get your templates and such built you shouldn't experience that much NFS I/O. You should allocate enough memory to your guest as to avoid virtual disk paging on your NFS storage.

  • Multiple local storage repositories in a standalone Oracle VM Server

    Hi, I have a server with two disk volumes created: RAID1(/dev/sdb3) and RAID10(/dev/sda1)
    In the RAID1 volume was installed the Oracle VM Server 2.2.1.
    The rest of the RAID1 volume is available in the /OVS storage repository structure.
    Then I setting up a second storage repository using the space of the RAID10 volume.
    Steps:
    # mkfs.ext3 /dev/sda1
    # /opt/ovs-agent-2.3/utils/repos.py --new /dev/sda1
    # /opt/ovs-agent-2.3/utils/repos.py -i
    # /opt/ovs-agent-2.3/utils/repos.py -l
    [   ] 25bfdcda-bad1-4836-ad72-d6204e56befb => /dev/sda1 -- RAID 10
    [ * ] b8ea3f06-10f4-4ea3-8fd9-0295ac6d46b4 => /dev/sdb3 -- RAID 1
    Finally I setup the fstab file to mount the RAID10 volume in boot-time in the /raid10 directory
    Reboot the server
    In the /raid10 directory I see the same directories names than the RAID1(/OVS) volume.
    Are these steps correct?
    When a new virtual machine is created with the Oracle VM Manager, how can I select the storage repository for this machine?
    Thanks in advance

    Hi,
    yes this is correct.
    Internally the ovs-agent will use the /var/ovs/mount/<ID> folders (you can check that with df -k) and not the /OVS directly.
    You do not have a chance in the current version to choose the repository. The ovs-agent will simply take the repository where there is the most free space.
    However after creating the VMs, you always (if shutdown) can simply move the contents of the folders (e.g. running_pool/name) to the other pool, and ovs-agent will automatically find the corresponding images (and update the configuration), when you start the VM.
    Regards
    Sebastian

  • 3rd party storage: AoE/Coraid integration

    #### LONG POST 1/3 ####
    Hi,
    We are working on AoE/Coraid (3rd party storage driver) integration within Oracle VM 3.x, we think that will be of use for the community and we'll love to share our work.
    But we discovered some issues and hope to have some help via this forum.
    So, to let you know how far we are and the current issue we have :
    1/ Our AoE RPM package is done (using SDK 3.0.2, waiting for 3.0.3 to be release) :
    # uname -a
    Linux ovm1 2.6.32.21-41xen #1 SMP Fri Sep 9 00:47:51 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
    # rpm -qa | grep aoe
    aoe-6-78
    2/ Our AoE init script is activated on boot and work as expected :
    # aoe-version
    aoetools:     32
    installed aoe driver:     78
    running aoe driver:     78
    # aoe-stat
    e66.3 2000.398GB eth1 1024 up
    ** First issue SOLVED :
    But ovs-agent complain each time we try to discover a server using Oracle Manager (running version 3.0.3 in case it may have an impact?) :
    [2012-01-19 03:11:39 30488] DEBUG (OVSCommons:124) discover_server: ()
    [2012-01-19 03:11:39 30488] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
    [2012-01-19 03:11:39 30488] DEBUG (OVSCommons:132) discover_server: call completed.
    [2012-01-19 03:11:40 30504] DEBUG (OVSCommons:124) discover_hardware: ()
    [2012-01-19 03:11:40 30504] ERROR (OVSCommons:143) catch_error: ERROR 0 @ 244 find_aoe_disks() Problems extracting AOE disk info
    Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py", line 178, in find_aoe_disks
    stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 615, in vi_exe_sync
    theChild     = VI_Process_OBJ( vi_errorAndLog_obj, False, args, relativeTimeoutInSecs, inputData_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 106, in __init__
    ,     0 )                    # creationflags               :: Windows only CreateProcess flag
    File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__
    errread, errwrite)
    File "/usr/lib64/python2.4/subprocess.py", line 1000, in executechild
    raise child_exception
    OSError: [Errno 2] No such file or directory
    Runtime errors occured [1]
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 141, in wrapper
    return func(*args)
    File "/opt/ovs-agent-3.0/OVSDiscoverHardware.py", line 81, in discover_hardware
    raise Exception(scsi_logmsg)
    Exception: ERROR 0 @ 244 find_aoe_disks() Problems extracting AOE disk info
    Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py", line 178, in find_aoe_disks
    stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 615, in vi_exe_sync
    theChild     = VI_Process_OBJ( vi_errorAndLog_obj, False, args, relativeTimeoutInSecs, inputData_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 106, in __init__
    ,     0 )                    # creationflags               :: Windows only CreateProcess flag
    File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__
    errread, errwrite)
    File "/usr/lib64/python2.4/subprocess.py", line 1000, in executechild
    raise child_exception
    OSError: [Errno 2] No such file or directory
    Runtime errors occured [1]
    We just discovered the st_ATAoverEthernet.py but it look like it is not able to see the available AoE LUNs.
    Is the script author (Mr Joshua Nicholas) working for Oracle ???
    We just fixed the issue above in file /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py :
    the subprocess call the "ata_id" but this program isn't in PATH !
    To test, we did this patch :
    diff -upr /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py.orig /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py
    # diff -upr st_ATAoverEthernet.py.orig st_ATAoverEthernet.py
    --- st_ATAoverEthernet.py.orig 2012-01-19 16:23:04.000000000 +0100
    +++ st_ATAoverEthernet.py 2012-01-19 11:30:45.000000000 +0100
    @@ -175,7 +175,7 @@ def find_aoe_disks( vi_errorAndLog_obj,
    aoe_disk_interface = aoe_stat_line_components[2]
    aoe_disk_interface_status = aoe_stat_line_components[4]
    - stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
    + stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ '/lib/udev/ata_id', '--export', aoe_devPath ], 10 )
    serial_cmpldRegEx = re.compile( '^ID_SERIAL=\s*' )
    rev_cmpldRegEx = re.compile( '^ID_REVISION=\s*' )
    It works, so finaly, we rollback to the last version of st_ATAoverEthernet.py and just (re)created the symlink : /sbin/ata_id -> /lib/udev/ata_id
    No more error messages in /var/log/ovs-agent.log as you can see :
    [2012-01-19 16:27:05 2607] DEBUG (OVSCommons:124) discover_server: ()
    [2012-01-19 16:27:05 2607] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
    [2012-01-19 16:27:05 2607] DEBUG (OVSCommons:132) discover_server: call completed.
    [2012-01-19 16:27:06 2623] DEBUG (OVSCommons:124) discover_hardware: ()
    [2012-01-19 16:27:06 2623] DEBUG (OVSCommons:132) discover_hardware: call completed.
    [2012-01-19 16:27:07 2672] DEBUG (OVSCommons:124) discover_network: ()
    [2012-01-19 16:27:07 2672] DEBUG (OVSCommons:132) discover_network: call completed.
    [2012-01-19 16:27:08 2673] DEBUG (OVSCommons:124) discover_storage_plugins: ()
    [2012-01-19 16:27:08 2673] DEBUG (OVSCommons:132) discover_storage_plugins: call completed.
    [2012-01-19 16:27:08 2674] DEBUG (OVSCommons:124) discover_physical_luns: ('',)
    [2012-01-19 16:27:08 2674] DEBUG (OVSCommons:132) discover_physical_luns: call completed.
    1/2 CONTINUE ON THE SECOND POST
    Edited by: 904919 on Jan 19, 2012 7:04 PM

    3/3 END OF THE POST
    Write Methods Invoked
    Class=InternalJobDbImpl vessel_id=6511 method=addTransactionIdentifier accessLevel=6
    Class=DiscoverManagerDbImpl vessel_id=165 method=discoverServer accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setCompletedStep accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setAssociatedHandles accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setContext accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setName accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setFoundryContext accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=onPersistableCreate accessLevel=6
    Class=HashMapDbImpl vessel_id=6528 method=remove accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setName accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setFoundryContext accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=onPersistableCreate accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setLifecycleState accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setRollbackLifecycleState accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setName accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setFoundryContext accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6541 method=notify accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setLifecycleState accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setRollbackLifecycleState accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setNumber accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setServer accessLevel=6
    Class=RootStatisticLogDbImpl vessel_id=117 method=createStatisticSubjectLog accessLevel=6
    Class=StatisticSubjectLogDbImpl vessel_id=6542 method=setStatisticSubject accessLevel=6
    Class=StatisticSubjectLogDbImpl vessel_id=6542 method=createAllStatisticTypeLogs accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6544 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6546 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6548 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6550 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6552 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6554 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6556 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6558 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6560 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6562 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6564 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6566 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6568 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6570 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6572 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6574 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6576 method=setType accessLevel=6
    Class=ServerStoppedEventDbImpl vessel_id=6578 method=notify accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setType accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setEncodedAgentPassword accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManagementInternetProtocolAddress accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setAgentVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBootGeneration accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setRpmVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setOvmVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setHostKernelRelease accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setHostKernelVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setHostname accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManagerUuid accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setPythonBindingVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createHypervisor accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setName accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setFoundryContext accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=onPersistableCreate accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setLifecycleState accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setRollbackLifecycleState accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setServer accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiler accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiledBy accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompileDomain accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiledDate accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setVersion accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=clearCapabilities accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=removeAllNtpServers accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setStatisticInterval accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setProductName accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManufacturer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setProductSerialNumber accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setSimpleName accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setSimpleName accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setMemory accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setProcessorSpeed accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNoExecuteFlag accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfThreadsPerCore accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfProcessorSockets accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfCoresPerProcessorSocket accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfProcessorCores accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfEnabledProcessorCores accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfPopulatedProcessorSockets accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBIOSReleaseDate accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBIOSVendor accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBIOSVersion accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setCpuModel accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setCpuModel accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setCpuModel accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setCpuModel accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setName accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setFoundryContext accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=onPersistableCreate accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setLifecycleState accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setRollbackLifecycleState accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setSimpleName accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setCpuCompatibilityGroup accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createStorageInitiator accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setName accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setFoundryContext accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=onPersistableCreate accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setLifecycleState accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setFoundryContext accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6625 method=notify accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setRollbackLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setSimpleName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setNumber accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setServer accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setInterfaceName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setMediaAccessControlAddress accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setMediaTransferUnit accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setDetails accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setFoundryContext accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6632 method=notify accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setRollbackLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setSimpleName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setNumber accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setServer accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setInterfaceName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setMediaAccessControlAddress accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setMediaTransferUnit accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setDetails accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setName accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setFoundryContext accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6641 method=notify accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setLifecycleState accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setRollbackLifecycleState accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setSimpleName accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setNumber accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setServer accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=addJobOperation accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setInterfaceName accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setInternetProtocolAddress accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setNetmask accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setAddressType accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=addEthernetPort accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setBondPort accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setMediaAccessControlAddress accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManagementMediaAccessControlAddress accessLevel=6
    Class=EthernetNetworkDbImpl vessel_id=2837 method=addNetworkPort accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setNetworkPortGroup accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setJobAsset accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
    Class=FileSystemPluginDbImpl vessel_id=2878 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
    Class=StorageArrayPluginDbImpl vessel_id=2843 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
    Class=FileSystemPluginDbImpl vessel_id=2872 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createLocalFileServer accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setName accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setFoundryContext accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=onPersistableCreate accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setLifecycleState accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setRollbackLifecycleState accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setStoragePlugin accessLevel=6
    Class=FileSystemPluginDbImpl vessel_id=2878 method=addStorageServer accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminHostname accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminUsername accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminPassword accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setSimpleName accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setServer accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setSimpleName accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setValidated accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createLocalStorageArray accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setName accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setFoundryContext accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=onPersistableCreate accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setLifecycleState accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setRollbackLifecycleState accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setStoragePlugin accessLevel=6
    Class=StorageArrayPluginDbImpl vessel_id=2843 method=addStorageServer accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setValidated accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setSimpleName accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=createVolumeGroup accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setName accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setFoundryContext accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=onPersistableCreate accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setLifecycleState accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setRollbackLifecycleState accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setStorageArray accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setSimpleName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setFoundryContext accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=onPersistableCreate accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setLifecycleState accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setRollbackLifecycleState accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setPage83Id accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setVolumeGroup accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=2856 method=addStorageElement accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setVendor accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setUserFriendlyName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setSimpleName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setSize accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setStorageElementType accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setFailedOperation accessLevel=6
    Class=DiscoverManagerDbImpl vessel_id=165 method=nextJobOperation accessLevel=6
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_6055E Discover target: ovm1, Discover failed with error: java.lang.NullPointerException
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanAddMissingStoragePath(ServerPhysicalLunDiscoverHandler.java:371)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanDiskProcess(ServerPhysicalLunDiscoverHandler.java:243)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.process(ServerPhysicalLunDiscoverHandler.java:195)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:442)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Thu Jan 19 16:35:04 CET 2012
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: ovm1, Discover failed with error: java.lang.NullPointerException
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanAddMissingStoragePath(ServerPhysicalLunDiscoverHandler.java:371)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanDiskProcess(ServerPhysicalLunDiscoverHandler.java:243)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.process(ServerPhysicalLunDiscoverHandler.java:195)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:442)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Thu Jan 19 16:35:04 CET 2012
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:457)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    End of Job
    If anyone have any suggestions... ?
    Thank you,
    Yacine

  • Strange - on one blade, /OVS is mounted twice

    Hi all
    Oracle VM 2.1.2
    On a 5 blade HP C3000 Enclosure, I'm trying to provide the shared /OVS file system. On 4 of the blades, OCFS is working correctly. Strangely, on one of the blades, despite an identical /etc/fstab, after booting, /OVS is mounted twice:
    df output
    /dev/mapper/lun1-oraclevm 67356672 1402880 65953792 3% /OVS
    /dev/cciss/c0d0p3 67356672 1402880 65953792 3% /OVS
    */etc/fstab*
    root@hpblade2 etc# more fstab
    LABEL=/ / ext3 defaults 1 1
    LABEL=/boot /boot ext3 defaults 1 2
    devpts /dev/pts devpts gid=5,mode=620 0 0
    tmpfs /dev/shm tmpfs defaults 0 0
    proc /proc proc defaults 0 0
    sysfs /sys sysfs defaults 0 0
    LABEL=SW-cciss/c0d0p5 swap swap defaults 0 0
    */dev/mapper/lun1-oraclevm /OVS ocfs2 sync,_netdev 1 0 # SAN*
    filerrac.ch.oracle.com:/vol/sct /mnt/sct nfs defaults 0 0
    To my best knowledge, fstab is the only file defining filesystems to be mounted upon startup.
    When I umount /OVS, the unwanted mount is removed, leaving the proper one. When I try to establish HA using VM Manager, the unwanted /OVS reappears....
    On this blade, for a first quick test before setting up OCFS2, I've set up (and deleted thereafter) a VM Server (Server Pool Master, Utility Server, Virtual Machine Server). Maybe the unwanted mount of /dev/cciss/c0d0p3 stems from this trial? Is there another file that could cause the unwanted mount?
    Thanks a lot
    Tino

    Alas, no success, see my steps and results below....
    After that, I've found a thread that sounds promising - [ovs-onlinerepo not working with multipath environment |http://forums.oracle.com/forums/thread.jspa?threadID=843783]. I realize I havn't mentioned multipath yet - sorry if this was crucial information.
    Anyway, I will check the solution path out and come back with outcome....
    ==> Quick update: Multipath does cause the problem. Commented /etc/multipath.conf out, booted.......and /OVS mounts like a dream. Haven't done the
    ==> other steps, yet.....
    Cheers, Tino
    Check Repositories
    root@hpblade2 ovs# more /etc/ovs/repositories
    # This configuration file was generated by ovs-makerepo
    # DO NOT EDIT
    reboot
    Stopping all Services
    root@hpblade2 etc]# service ovs-agent stop
    OVSAgentServer shutdown...
    OVSAgentServer stopped.
    root@hpblade2 ~]# /etc/init.d/ovsrepositories stop
    Stopping OVS Storage Repository Mounter...
    OVS Storage Repository Mounter Shutdown: [  OK  ]
    root@hpblade2 ~]# service ocfs2 stop
    Stopping Oracle Cluster File System (OCFS2) [  OK  ]
    root@hpblade2 ~]# service o2cb stop
    Stopping O2CB cluster ocfs2: OK
    Unmounting ocfs2_dlmfs filesystem: OK
    Unloading module "ocfs2_dlmfs": OK
    Unmounting configfs filesystem: OK
    Unloading module "configfs": OK
    Starting all Services
    root@hpblade2 ~]# service o2cb start
    Loading module "configfs": OK
    Mounting configfs filesystem at /sys/kernel/config: OK
    Loading module "ocfs2_nodemanager": OK
    Loading module "ocfs2_dlm": OK
    Loading module "ocfs2_dlmfs": OK
    Mounting ocfs2_dlmfs filesystem at /dlm: OK
    Starting O2CB cluster ocfs2: OK
    root@hpblade2 ~]# service ocfs2 start
    Starting Oracle Cluster File System (OCFS2) [  OK  ]
    root@hpblade2 ~]# /etc/init.d/ovsrepositories start
    Starting OVS Storage Repository Mounter...
    OVS Storage Repository Mounter Startup: [  OK  ]
    root@hpblade2 ~]# service ovs-agent start
    OVSAgentServer is now starting...
    OVSAgentServer started.
    Status Services
    root@hpblade2 ~]# service ovs-agent status
    ok! process OVSPolicyServer exists.
    ok! process OVSMonitorServer exists.
    ok! process OVSAgentServer exists.
    ok! process OVSLogServer exists.
    ok! OVSAgentServer is alive.
    root@hpblade2 ~]# /etc/init.d/ovsrepositories status
    OVS Storage Repository Mounter Loaded... [  OK  ]
    root@hpblade2 ~]# service ocfs2 status
    Configured OCFS2 mountpoints: /OVS
    Active OCFS2 mountpoints: /OVS
    root@hpblade2 ~]# service o2cb status
    Module "configfs": Loaded
    Filesystem "configfs": Mounted
    Module "ocfs2_nodemanager": Loaded
    Module "ocfs2_dlm": Loaded
    Module "ocfs2_dlmfs": Loaded
    Filesystem "ocfs2_dlmfs": Mounted
    Checking O2CB cluster ocfs2: Online
    Heartbeat dead threshold: 31
    Network idle timeout: 30000
    Network keepalive delay: 2000
    Network reconnect delay: 2000
    Checking O2CB heartbeat: Active
    Make Repository
    root@hpblade2 ~]# /usr/lib/ovs/ovs-makerepo /dev/mapper/lun1-oraclevm C "cluster root"
    Repository /dev/mapper/lun1-oraclevm already initialized
    Updating local repository list.
    ovs-makerepo complete
    root@hpblade2 ~]# more /etc/ovs/repositories
    # This configuration file was generated by ovs-makerepo
    # DO NOT EDIT
    @A08F5B4E10D546F0A1071638BFF5FEDA /dev/mapper/lun1-oraclevm
    root@hpblade2 ~]# /usr/lib/ovs/ovs-cluster-check master alter-fstab
    Backing up original /etc/fstab to /tmp/fstab.wDTJg30531
    Removing /OVS mounts in /etc/fstab
    O2CB cluster ocfs2 already online
    Cluster setup complete.
    Test
    The boot sequence shows:
    Starting OVS Storage Repository Mounter....
    Mounting repository @A08.....FEDA from /dev/mapper/lun1-oraclevm
    mount.ocfs2: Device or resource busy while mounting /dev/sdd on /OVS.
    Check 'dmesg' for more information on this error.
    Failed to mount a08....feda at /OVS
    Edited by: cbourbou on Apr 15, 2009 8:04 AM

  • OVM 2.2 and NFS Repository Problems

    Hi All.
    I have recently started trying to upgrade our installation to 2.2
    but have run into a few problems, mostly relating to the different
    way that storage repositories are handled in comparison to 2.1.5.
    We use NFS here to provide shared storage to the pools.
    I wanted to setup a new two node server pool (with HA), so I upgraded
    one of the servers to from 2.1.5 to 2.2 to act as pool master. That
    worked ok and this server seems to be working fine in isolation:
    master# /opt/ovs-agent-2.3/utils/repos.py -l
    [ * ] 865a2e52-db29-48f1-98a0-98f985b3065c => augustus:/vol/OVS_pv_vpn
    master# df /OVS
    Filesystem 1K-blocks Used Available Use% Mounted on
    augustus:/vol/OVS_pv_vpn
                   47185920 16083008 31102912 35% /var/ovs/mount/865A2E52DB2948F198A098F985B3065C
    (I then successfully launched a VM on it.)
    The problem is when I try to add a second server to the pool. I did
    a fresh install of 2.2 and configured the storage repository to be the
    same as that used on the first node:
    vm1# /opt/ovs-agent-2.3/utils/repos.py --new augustus:/vol/OVS_pv_vpn
    vm1# /opt/ovs-agent-2.3/utils/repos.py -r 865a2e52-db29-48f1-98a0-98f985b3065c
    vm1# /opt/ovs-agent-2.3/utils/repos.py -l
    [ R ] 865a2e52-db29-48f1-98a0-98f985b3065c => augustus:/vol/OVS_pv_vpn
    When I try to add this server into the pool using the management GUI, I get
    this error:
    OVM-1011 Oracle VM Server 172.22.36.24 operation HA Check Prerequisite failed: failed:<Exception: ha_precheck_storage_mount failed:<Exception: /OVS must be mounted.> .
    Running "repos.py -i" yields:
    Cluster not available.
    Seems like a chicken and egg problem: I can't add the server to the pool without a
    mounted /OVS, but mounting /OVS is done by adding it to the pool? Or do I have that
    wrong?
    More generally, I'm a bit confused at how the repositories are
    supposed to be managed under 2.2.
    For exaple, the /etc/init.d/ovsrepositories script is still present,
    but is it still used? When I run it, it prints a couple of errors and
    doesn't seem to mount anything:
    vm1# service ovsrepositories start
    /etc/ovs/repositories does not exist
    Starting OVS Storage Repository Mounter...
    /etc/init.d/ovsrepositories: line 111: /etc/ovs/repositories: No such file or directory
    /etc/init.d/ovsrepositories: line 111: /etc/ovs/repositories: No such file or directory
    OVS Storage Repository Mounter Startup: [  OK  ]
    Should this service be turned off? It seem that ovs-agent now takes
    responsibility for mounting the repositories.
    As an aside, my Manager is still running 2.1.5 - is that part of the
    problem here? Is it safe to upgrade the manager to 2.2 while I still
    have a couple of pools running 2.1.5 servers?
    Thanks in adavance,
    Robert.

    rns wrote:
    Seems like a chicken and egg problem: I can't add the server to the pool without a
    mounted /OVS, but mounting /OVS is done by adding it to the pool? Or do I have that
    wrong?You have that wrong -- the /OVS mount point is created by ovs-agent while the server is added to the pool. You just need access to the shared storage.
    For exaple, the /etc/init.d/ovsrepositories script is still present,
    but is it still used?No, it is not. ovs-agent now handles the storage repositories.
    As an aside, my Manager is still running 2.1.5 - is that part of the
    problem here? Yes. You absolutely need to upgrade your Manager first to 2.2 before attempting to create/manage a 2.2-based pool. The 2.1.5 Manager doesn't know how to tell the ovs-agent how to create/join a pool properly. The upgrade process is detailed in [the ULN FAQ|https://linux.oracle.com/uln_faq.html#10].

  • Simple Question but have yet to find any info

    Let say I am setting up a database on one machine and I want it to live migrate to another - I have 4 luns - lets say /OVS for shared reporsitory - /pr01 - oracle binaries - /prdb for database files and /prlg for logs -
    I know I need to make the OVS ocfs2 - now do I create 2 Vm's and how do I present the other luns to the server - Do I have to ocfs2 these also ? - or do I just edit vm.cfg and add them in as say ext3 filesystems ?
    Thanks for help - This is not RAC

    Greetings,
    Q: Let say I am setting up a database on one machine and I want it to live migrate to another - I have 4 luns - lets say /OVS for shared repository - /pr01 - oracle binaries - /prdb for database files and /prlg for logs -
    I know I need to make the OVS ocfs2 - now do I create 2 Vm's and how do I present the other luns to the server - Do I have to ocfs2 these also ? - or do I just edit vm.cfg and add them in as say ext3 filesystems?
    A: Please note that you have two option, a) 4 LUNs or b) use 1 LUN for /OVS and 3 shared virtual disks, i.e. pr01.img, prdb.img and prlg.img located in the /OVS/SharedDisk directory. Let's break down each option.
    Q: How do I present the other luns to the server.
    A: You present all the LUNs to each "Oracle VM server" using the identical configuration, i.e. please see http://itnewscast.com/chapter-6-oracle-vm-22-san-iscsi-and-nfs-backend-storage-configurations#SAN_Storage_Repository_Configuration for configuration details.
    Q: Do I have to ocfs2 these also?
    A: If you mean using OCFS2 for the /pr01,/prdb and /prlg LUNs, the answer is not really. You could provision the LUNs and format each LUN with ext3, then present the LUNs to each host and then in each guest in it's vm.cfg file. Please see http://itnewscast.com/chapter-6-oracle-vm-22-san-iscsi-and-nfs-backend-storage-configurations#SAN_Storage_Repository_Configuration for the hosts and http://itnewscast.com/chapter-6-oracle-vm-22-san-iscsi-and-nfs-backend-storage-configurations#Oracle_VM_Guest_Front-end_Storage for the guest configuration details.
    Please note that the option to use shared virtual disks for the /pr01,/prdb and /prlg directories would create a separate file backed block device, i.e. pr01.img, prdb.img and prlg.img file for each directory in the /OVS storage repository located in the /OVS/SharedDisk/ directory. Shared virtual disks are available and manageable in Oracle VM Manager. This option would only require one LUN, i.e. for the /OVS root storage repository. Live Migration with this configuration is an integrated feature, i.e. nothing to configure other than a root storage repository, i.e. http://itnewscast.com/chapter-6-oracle-vm-22-san-iscsi-and-nfs-backend-storage-configurations#SAN_Storage_Repository_Configuration
    Q: do I just edit vm.cfg and add them in as say ext3 filesystems?
    A: Yes, each option (luns or shared v disks) will require entries for each of the LUNs or shared virtual disks in each guest's vm.cfg file. Ext3 can be used for each lun.
    I hope this helps!
    Respectfully,
    Roddy
    Edited by: Roddy Rodstein on May 4, 2010 3:44 PM

  • OVM 3 and multipaths

    Hi,
    Just noticed this behavior when re-installing our OVM servers due to other issues. It doesn't appear to like aliases instead of user_friendly_names. When I discover the server with the following set:
    mpathf (36001438005ded2250000700003480000) dm-6 HP,HSV400
    size=220G features='1 queue_if_no_path' hwhandler='0' wp=rw
    `-+- policy='round-robin 0' prio=1 status=enabled
    |- 3:0:1:2 sdh 8:112 active ready running
    |- 3:0:0:2 sdc 8:32 active ready running
    |- 3:0:2:2 sdm 8:192 active ready running
    |- 3:0:3:2 sdr 65:16 active ready running
    |- 4:0:0:2 sdw 65:96 active ready running
    |- 4:0:1:2 sdab 65:176 active ready running
    |- 4:0:2:2 sdag 66:0 active ready running
    `- 4:0:3:2 sdal 66:80 active ready running
    It works. When I setup 'nice' names, it doesn't:
    san_cluster_1 (36001438005ded2250000700003480000) dm-6 HP,HSV400
    size=220G features='1 queue_if_no_path' hwhandler='0' wp=rw
    `-+- policy='round-robin 0' prio=1 status=enabled
    |- 3:0:1:2 sdh 8:112 active ready running
    |- 3:0:0:2 sdc 8:32 active ready running
    |- 3:0:2:2 sdm 8:192 active ready running
    |- 3:0:3:2 sdr 65:16 active ready running
    |- 4:0:0:2 sdw 65:96 active ready running
    |- 4:0:1:2 sdab 65:176 active ready running
    |- 4:0:2:2 sdag 66:0 active ready running
    `- 4:0:3:2 sdal 66:80 active ready running
    Bombs out with:
    [2011-10-05 16:53:52 14729] ERROR (OVSCommons:142) catch_error: ERROR 0 @ 522 parse_multipath_conf_multipaths() found unsupported multipath 'multipath' '{' count(1811)
    ERROR 1 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1813)]
    ERROR 2 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1815)]
    ERROR 3 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1816)]
    ERROR 4 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1818)]
    ERROR 5 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1820)]
    ERROR 6 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1822)]
    ERROR 7 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1823)]
    ERROR 8 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1825)]
    ERROR 9 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1827)]
    ERROR 10 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1829)]
    ERROR 11 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1830)]
    ERROR 12 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1832)]
    ERROR 13 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1834)]
    ERROR 14 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1836)]
    ERROR 15 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1837)]
    ERROR 16 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1838)]
    ERROR 17 @ 137 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 134, in add_all_block_data
    blkdev_LIST = filter_blk_dev_list( vi_errorAndLog_obj, blkdev_LIST, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 118, in filter_blk_dev_list
    for mpConf_blkLstDevNode in mpConf_blacklistInfo.mDevNode_LIST:
    AttributeError: 'NoneType' object has no attribute 'mDevNode_LIST'
    ERROR 18 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 184, in populate_blk_dev_info_dict
    for mpConf_blkLstDev in mpConf_blacklistInfo.mDevice_LIST:
    AttributeError: 'NoneType' object has no attribute 'mDevice_LIST'
    Tried with / without special characters. Same for both. Weird.
    Edited to say as well, with OVM 3.0.1 these error messages are displayed back to the OVM Manager GUI, with OVM 3.0.2 just a bunch of java errors get displayed instead - have to go to the OVM server to get the actual issue..
    tarting operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
    Setting Context to model only in job with id=1317826389157
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '44:45:4c:4c:30:00:10:4b:80:47:c8:c0:4f:35:33:4a'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '44:45:4c:4c:30:00:10:4b:80:47:c8:c0:4f:35:33:4a'.
    Operation 'Server Set Statistic Interval' in non-job running context, not adding it to object '44:45:4c:4c:30:00:10:4b:80:47:c8:c0:4f:35:33:4a'.
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 44:45:4c:4c:30:00:10:4b:80:47:c8:c0:4f:35:33:4a failed. OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Wed Oct 05 16:53:11 CEST 2011
    Wed Oct 05 16:53:11 CEST 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
    at com.oracle.ovm.mgr.action.ActionEngine.sendDiscoverCommand(ActionEngine.java:291)
    at com.oracle.ovm.mgr.action.ServerAction.getHardwareInfo(ServerAction.java:101)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:316)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:46)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:50)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:435)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:420)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:405)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:223)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Wed Oct 05 16:53:11 CEST 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:752)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
    ... 30 more
    Edited by: dave on Oct 5, 2011 7:59 AM

    Hello!
    Having very strange problem which is similar. Can not avoid discovery error even with setting user_friendly_names=no. What could be the reason? Have a Metalink account, but unfortunately could not open an event on Oracle VM product right now because we are just running a POC with IBM Innovation center on this configuration.
    Appreciate your help!
    ovs-agent.log ===========================================================================
    Runtime errors occured [18]
    [2011-10-16 00:11:14 17583] DEBUG (OVSCommons:123) discover_server: ()
    [2011-10-16 00:11:14 17583] DEBUG (OVSCommons:131) discover_server: call completed.
    [2011-10-16 00:11:18 17618] DEBUG (OVSCommons:123) discover_hardware: ()
    [2011-10-16 00:11:19 17618] ERROR (OVSCommons:142) catch_error: ERROR 0 @ 522 parse_multipath_conf_multipaths() found unsupported multipath 'multipath' '{' count(1788)
    ERROR 1 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1790)]
    ERROR 2 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1791)]
    ERROR 3 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1793)]
    ERROR 4 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1795)]
    ERROR 5 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1796)]
    ERROR 6 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1798)]
    ERROR 7 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1800)]
    ERROR 8 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1801)]
    ERROR 9 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1803)]
    ERROR 10 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1805)]
    ERROR 11 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1806)]
    ERROR 12 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1808)]
    ERROR 13 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1810)]
    ERROR 14 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1811)]
    ERROR 15 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1812)]
    ERROR 16 @ 137 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 134, in add_all_block_data
    blkdev_LIST = filter_blk_dev_list( vi_errorAndLog_obj, blkdev_LIST, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 118, in filter_blk_dev_list
    for mpConf_blkLstDevNode in mpConf_blacklistInfo.mDevNode_LIST:
    AttributeError: 'NoneType' object has no attribute 'mDevNode_LIST'
    ERROR 17 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 184, in populate_blk_dev_info_dict
    for mpConf_blkLstDev in mpConf_blacklistInfo.mDevice_LIST:
    AttributeError: 'NoneType' object has no attribute 'mDevice_LIST'
    Runtime errors occured [18]
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
    return func(*args)
    File "/opt/ovs-agent-3.0/OVSDiscoverHardware.py", line 81, in discover_hardware
    raise Exception(scsi_logmsg)
    Exception: ERROR 0 @ 522 parse_multipath_conf_multipaths() found unsupported multipath 'multipath' '{' count(1788)
    ERROR 1 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1790)]
    ERROR 2 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1791)]
    ERROR 3 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1793)]
    ERROR 4 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1795)]
    ERROR 5 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1796)]
    ERROR 6 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1798)]
    ERROR 7 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1800)]
    ERROR 8 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1801)]
    ERROR 9 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1803)]
    ERROR 10 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1805)]
    ERROR 11 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1806)]
    ERROR 12 @ 639 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected section 'multipath' [count(1808)]
    ERROR 13 @ 597 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 2 [count(1810)]
    ERROR 14 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1811)]
    ERROR 15 @ 586 parse_multipath_conf_lines_list() multipathCnfLines contains unexpected format 1 [count(1812)]
    ERROR 16 @ 137 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 134, in add_all_block_data
    blkdev_LIST = filter_blk_dev_list( vi_errorAndLog_obj, blkdev_LIST, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 118, in filter_blk_dev_list
    for mpConf_blkLstDevNode in mpConf_blacklistInfo.mDevNode_LIST:
    AttributeError: 'NoneType' object has no attribute 'mDevNode_LIST'
    ERROR 17 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 184, in populate_blk_dev_info_dict
    for mpConf_blkLstDev in mpConf_blacklistInfo.mDevice_LIST:
    AttributeError: 'NoneType' object has no attribute 'mDevice_LIST'
    multipath.conf: ===========================================================================
    ## IMPORTANT for OVS this must be no. OVS does not support user friendly
    ## names and instead uses the WWIDs as names.
    defaults {
    polling_interval 30
    failback immediate
    no_path_retry 5
    rr_min_io 100
    path_checker tur
    user_friendly_names no
    # SVC
    device {
    vendor "IBM"
    product "2145"
    path_grouping_policy group_by_prio
    prio_callout "/sbin/mpath_prio_alua /dev/%n"
    # List of device names to discard as not multipath candidates
    ## IMPORTANT for OVS do not remove the black listed devices.
    blacklist {
         wwid "3600605b002eb737015c1c4e92ba3c828"
    multipaths {
         multipath {
    wwid 3600507680281007240000000000000d9
         multipath {
    wwid 3600507680281007240000000000000dc
         multipath {
    wwid 3600507680281007240000000000000db
         multipath {
    wwid 3600507680281007240000000000000dd
         multipath {
    wwid 3600507680281007240000000000000da
    multipath -ll: ===========================================================================
    [root@oracle-vms log]# multipath -ll
    mpathe (3600507680281007240000000000000da) dm-3 IBM,2145
    size=1.0T features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=enabled
    | |- 3:0:1:2 sdh 8:112 active ready running
    | |- 3:0:3:2 sdr 65:16 active ready running
    | |- 4:0:1:2 sdab 65:176 active ready running
    | |- 4:0:3:2 sdal 66:80 active ready running
    | |- 5:0:3:2 sdav 66:240 active ready running
    | `- 6:0:3:2 sdbf 67:144 active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
    |- 3:0:0:2 sdc 8:32 active ready running
    |- 3:0:2:2 sdm 8:192 active ready running
    |- 4:0:0:2 sdw 65:96 active ready running
    |- 4:0:2:2 sdag 66:0 active ready running
    |- 5:0:0:2 sdaq 66:160 active ready running
    `- 6:0:0:2 sdba 67:64 active ready running
    mpathd (3600507680281007240000000000000dd) dm-1 IBM,2145
    size=1.0T features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=enabled
    | |- 3:0:0:5 sdf 8:80 active ready running
    | |- 3:0:2:5 sdp 8:240 active ready running
    | |- 4:0:0:5 sdz 65:144 active ready running
    | |- 4:0:2:5 sdaj 66:48 active ready running
    | |- 5:0:0:5 sdat 66:208 active ready running
    | `- 6:0:0:5 sdbd 67:112 active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
    |- 3:0:1:5 sdk 8:160 active ready running
    |- 3:0:3:5 sdu 65:64 active ready running
    |- 4:0:1:5 sdae 65:224 active ready running
    |- 4:0:3:5 sdao 66:128 active ready running
    |- 5:0:3:5 sday 67:32 active ready running
    `- 6:0:3:5 sdbi 67:192 active ready running
    mpathc (3600507680281007240000000000000dc) dm-2 IBM,2145
    size=1.0T features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=enabled
    | |- 3:0:1:4 sdj 8:144 active ready running
    | |- 3:0:3:4 sdt 65:48 active ready running
    | |- 4:0:1:4 sdad 65:208 active ready running
    | |- 4:0:3:4 sdan 66:112 active ready running
    | |- 5:0:3:4 sdax 67:16 active ready running
    | `- 6:0:3:4 sdbh 67:176 active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
    |- 3:0:0:4 sde 8:64 active ready running
    |- 3:0:2:4 sdo 8:224 active ready running
    |- 4:0:0:4 sdy 65:128 active ready running
    |- 4:0:2:4 sdai 66:32 active ready running
    |- 5:0:0:4 sdas 66:192 active ready running
    `- 6:0:0:4 sdbc 67:96 active ready running
    mpathb (3600507680281007240000000000000db) dm-4 IBM,2145
    size=1.0T features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=enabled
    | |- 3:0:0:3 sdd 8:48 active ready running
    | |- 3:0:2:3 sdn 8:208 active ready running
    | |- 4:0:0:3 sdx 65:112 active ready running
    | |- 4:0:2:3 sdah 66:16 active ready running
    | |- 5:0:0:3 sdar 66:176 active ready running
    | `- 6:0:0:3 sdbb 67:80 active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
    |- 3:0:1:3 sdi 8:128 active ready running
    |- 3:0:3:3 sds 65:32 active ready running
    |- 4:0:1:3 sdac 65:192 active ready running
    |- 4:0:3:3 sdam 66:96 active ready running
    |- 5:0:3:3 sdaw 67:0 active ready running
    `- 6:0:3:3 sdbg 67:160 active ready running
    mpatha (3600507680281007240000000000000d9) dm-0 IBM,2145
    size=500G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=enabled
    | |- 3:0:0:1 sdb 8:16 active ready running
    | |- 3:0:2:1 sdl 8:176 active ready running
    | |- 4:0:0:1 sdv 65:80 active ready running
    | |- 4:0:2:1 sdaf 65:240 active ready running
    | |- 5:0:0:1 sdap 66:144 active ready running
    | `- 6:0:0:1 sdaz 67:48 active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
    |- 3:0:1:1 sdg 8:96 active ready running
    |- 3:0:3:1 sdq 65:0 active ready running
    |- 4:0:1:1 sdaa 65:160 active ready running
    |- 4:0:3:1 sdak 66:64 active ready running
    |- 5:0:3:1 sdau 66:224 active ready running
    `- 6:0:3:1 sdbe 67:128 active ready running
    Regards,
    Kirill

  • OVM server Discovery fails

    When I attempt to discover one of my OVM servers I'm getting a python(?) error during the storage discovery phase.
    Anyone have any ideas how to resolve this?
    Thanks!
    warning icon     
    Job Construction Phase
    begin()
    Appended operation 'Discover Manager Server Discover' to object 'OVM Foundry : Discover Manager'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Operation: Discover Manager Server Discover
    Job Running Phase at 12:43 on Thu, Sep 15, 2011
    Job Participants: []
    Actioner
    Starting operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
    Setting Context to model only in job with id=1316119397274
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
    Operation 'Server Set Statistic Interval' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec failed. OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
    if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
    AttributeError: 'NoneType' object has no attribute 'search'
    Runtime errors occured [1]
    Thu Sep 15 12:43:18 AKDT 2011
    Thu Sep 15 12:43:18 AKDT 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
    at com.oracle.ovm.mgr.action.ActionEngine.sendDiscoverCommand(ActionEngine.java:291)
    at com.oracle.ovm.mgr.action.ServerAction.getHardwareInfo(ServerAction.java:101)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:316)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:46)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:50)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:433)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
    if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
    AttributeError: 'NoneType' object has no attribute 'search'
    Runtime errors occured [1]
    Thu Sep 15 12:43:18 AKDT 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:748)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
    ... 30 more
    FailedOperationCleanup
    Starting failed operation 'Discover Manager Server Discover' cleanup on object 'OVM Foundry : Discover Manager'
    Complete rollback operation 'Discover Manager Server Discover' completed with direction=OVM Foundry : Discover Manager
    Rollbacker
    Objects To Be Rolled Back
    Object (CREATED): [InternalPort] network.InternalPort (1) in 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
    Object (CREATED): [LocalStorageInitiator] storage.LocalStorageInitiator in 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
    Object (CREATED): [Server] 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Object (CREATED): [XenHypervisor] Hypervisor in 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_4010E Attempt to send command: discover_hardware to server: 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec failed. OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
    if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
    AttributeError: 'NoneType' object has no attribute 'search'
    Runtime errors occured [1]
    Thu Sep 15 12:43:18 AKDT 2011
    Thu Sep 15 12:43:18 AKDT 2011
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec failed. OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
    if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
    AttributeError: 'NoneType' object has no attribute 'search'
    Runtime errors occured [1]
    Thu Sep 15 12:43:18 AKDT 2011
    Thu Sep 15 12:43:18 AKDT 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
    at com.oracle.ovm.mgr.action.ActionEngine.sendDiscoverCommand(ActionEngine.java:291)
    at com.oracle.ovm.mgr.action.ServerAction.getHardwareInfo(ServerAction.java:101)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:316)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:46)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:50)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:433)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
    populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
    if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
    AttributeError: 'NoneType' object has no attribute 'search'
    Runtime errors occured [1]
    Thu Sep 15 12:43:18 AKDT 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:748)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
    ... 30 more
    End of Job
    ----------

    This is usually due to either of the following issues (not enough information to determine if this is your problem):
    1. The IP addresses you are using as the IPs for the Oracle VM servers being discovered are somehow incorrect. For instance, I sometimes typo one of the octets in the IP address IE: I meant to type 10.11.12.100, but instead messed up the third octet by typing a "21" instead of a "12" (just an example).
    2. The password you provided for the "Oracle VM Agent Password" in the discovery dialog is incorrect. There are several reasons this may be happening, but the way to ensure the ovs-agent has the same password you think it should is by logging into each Oracle VM server and changing the ovs-agent password for BOTH "admin" AND "oracle" users. This is done using the following command on each Oracle VM server:
    /usr/sbin/ovs-agent-passwd admin
    /usr/sbin/ovs-agent-passwd oracle
    Both of the above will prompt for a password - use the same password for both and ensure you do this on all your Oracle VM servers.
    Here is how you verify that the passwords you just changed work:
    /opt/ovs-agent-3.0/utils/do_rpc.py https://admin:<new passwd>@<your OVM server>:8899 echo ""
    /opt/ovs-agent-3.0/utils/do_rpc.py https://oracle:<new passwd>@<your OVM server>:8899 echo ""
    The above commands will return the following if the passwords are correct (anything else, no matter what error it returns means the password is not what you expect it to be):
    echo [''] =>
    success:echo=
    Hope this answer helps...
    -Greg

  • Exception: Could not find '/OVS/running_pool/30_Test02' in any storage repo

    when try to power on an virtual machine of Win 2003 server OS,it failed.
    And the log said:failed:<Exception: Could not find '/OVS/running_pool/30_Test02' in any storage repository.>
    Who can tell me the reason ?
    Thanks a lot,
    Mary

    login Oracle VM server to make sure that image/vm.cfg files are under /OVS/running_pool/30_Test02.
    what output if you issue command on Oracle VM Server?
    # cd /OVS/running_pool/30_Test02
    # xm create -c your_configuration_file.cfg
    Please post info in /var/log/xen/xend.log if any error.
    Message was edited by:
    Changhai

  • Ovs 3.2.2 rediscover storage

    Hello,
    Is it possible to move one physical storage under ovm server to a new ovm server and rediscover it ?
    Like i had old install of ovs with physical storage (where there are Iso files, VMs, ...) and need to change hardware,
    In the new server, is it possible to add my old storage (old disk) , discover it and present repository ?
    My ovs (new) has 3 disks, 2 new of *500gb* each and the old one *1Tb*
    Actually i am not able to see the old disk in the manager, but i see the new ones ( 500gb, 500gb ).
    i also tried
    dd if=/dev/zero of=/dev/mapper/SATA_xxxx bs=1M count=100
    and
    reboot
    still not able to see it in ovm.
    also it was appearing when typing blkid and had ocfs2 type
    but it is no more there
    should i make it raw ? how ? to be have it in the manager.
    Edited by: Joseph on Apr 27, 2013 9:49 PM
    I just removed the new disks from storage but manager show them again
    how to refresh info in ovs or ovs-agent or refresh storage info in manager ?
    What is refresh time between manager and agent ?
    Any idea ?
    Edited by: Joseph on Apr 27, 2013 9:49 PM

    I see the old disk in storage tab in manager
    After storage refresh from manager here is the log
    Job Construction Phase
    Job ID: 1367099943024
    begin()
    Appended operation 'FileSystem refresh' to object '0004fb00000500008f110d1a40af9537'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (IN_USE): [LocalFileSystem] 0004fb00000500008f110d1a40af9537
    Operation: FileSystem refresh
    Job Running Phase at 2013-04-27 21:59:03,024
    Job Participants: [00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff (ovsctech)]
    Actioner
    21:59:05,135: Starting operation 'FileSystem refresh' on object '0004fb00000500008f110d1a40af9537'
    Setting Context to model only in job with id=1367099943024
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: ocfs2_get_meta_data to server: ovsctech failed. OVMAPI_4004E Server Failed Command: ocfs2_get_meta_data /dev/mapper/SATA_WDC_WD10EARX-00_WD-WMC0T0533574 .ovsrepo, Status: org.apache.xmlrpc.XmlRpcException: exceptions.OSError:(0, 'Error') [Sat Apr 27 21:59:05 GMT 2013] [Sat Apr 27 21:59:05 GMT 2013]
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:512)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:464)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:390)
    at com.oracle.ovm.mgr.action.StorageAction.getOcfs2Metadata(StorageAction.java:165)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverOcfs2FileSystem(FileSystemRefresh.java:196)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:91)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1156)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:865)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:244)
    at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:230)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:322)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1340)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:106)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:92)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:752)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:467)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:525)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: ocfs2_get_meta_data /dev/mapper/SATA_WDC_WD10EARX-00_WD-WMC0T0533574 .ovsrepo, Status: org.apache.xmlrpc.XmlRpcException: exceptions.OSError:(0, 'Error') [Sat Apr 27 21:59:05 GMT 2013]
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:803)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:508)
    ... 32 more
    FailedOperationCleanup
    Starting failed operation 'FileSystem refresh' cleanup on object '0004fb00000500008f110d1a40af9537'
    Complete rollback operation 'FileSystem refresh' cleanup on object '0004fb00000500008f110d1a40af9537'
    Rollbacker
    21:59:10,294: Starting rollbacker...
    Executing rollback operation 'FileSystem refresh' on object '0004fb00000500008f110d1a40af9537'
    Complete rollback operation 'FileSystem refresh' completed with direction=DONE
    21:59:10,392: Rollbacker completed...
    Objects To Be Rolled Back
    Object (IN_USE): [LocalFileSystem] 0004fb00000500008f110d1a40af9537
    Write Methods Invoked
    21:59:04,527 Class=InternalJobDbImpl vessel_id=1006 method=addTransactionIdentifier accessLevel=6 owningTx=1367099944526
    21:59:04,556 Class=LocalFileSystemDbImpl vessel_id=711 method=refresh accessLevel=6 owningTx=1367099944526
    21:59:04,764 Class=InternalJobDbImpl vessel_id=1006 method=setCompletedStep accessLevel=6 owningTx=1367099944526
    21:59:04,772 Class=InternalJobDbImpl vessel_id=1006 method=setAssociatedHandles accessLevel=6 owningTx=1367099944526
    21:59:05,164 Class=InternalJobDbImpl vessel_id=1006 method=setContext accessLevel=6 owningTx=1367099944526
    21:59:05,605 Class=LocalFileSystemDbImpl vessel_id=711 method=nextJobOperation accessLevel=6 owningTx=1367099944526
    21:59:05,605 Class=InternalJobDbImpl vessel_id=1006 method=setFailedOperation accessLevel=6 owningTx=1367099944526
    21:59:10,317 Class=LocalFileSystemDbImpl vessel_id=711 method=nextJobOperation accessLevel=6 owningTx=1367099944526
    21:59:10,392 Class=LocalFileSystemDbImpl vessel_id=711 method=nextJobOperation accessLevel=6 owningTx=1367099944526
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_4010E Attempt to send command: ocfs2_get_meta_data to server: ovsctech failed. OVMAPI_4004E Server Failed Command: ocfs2_get_meta_data /dev/mapper/SATA_WDC_WD10EARX-00_WD-WMC0T0533574 .ovsrepo, Status: org.apache.xmlrpc.XmlRpcException: exceptions.OSError:(0, 'Error') [Sat Apr 27 21:59:05 GMT 2013] [Sat Apr 27 21:59:05 GMT 2013]
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: ocfs2_get_meta_data to server: ovsctech failed. OVMAPI_4004E Server Failed Command: ocfs2_get_meta_data /dev/mapper/SATA_WDC_WD10EARX-00_WD-WMC0T0533574 .ovsrepo, Status: org.apache.xmlrpc.XmlRpcException: exceptions.OSError:(0, 'Error') [Sat Apr 27 21:59:05 GMT 2013] [Sat Apr 27 21:59:05 GMT 2013]
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:512)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:464)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:390)
    at com.oracle.ovm.mgr.action.StorageAction.getOcfs2Metadata(StorageAction.java:165)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverOcfs2FileSystem(FileSystemRefresh.java:196)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:91)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1156)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:865)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:244)
    at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:230)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:322)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1340)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:356)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:333)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:106)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:92)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:752)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:467)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:525)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: ocfs2_get_meta_data /dev/mapper/SATA_WDC_WD10EARX-00_WD-WMC0T0533574 .ovsrepo, Status: org.apache.xmlrpc.XmlRpcException: exceptions.OSError:(0, 'Error') [Sat Apr 27 21:59:05 GMT 2013]
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:803)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:508)
    ... 32 more
    End of Job
    ----------

  • Can a muliple OVS directories can be used when 2GB of storage is available

    Hello,
    My plan is to use 4 oracle virtual servers to run many guest machine, and to migrate guests from one server to another ( when needed ).
    to support this, I also have an Iscsi storage with 4TeraByte of space.
    I want to allocate the entire storage to be used for current guests and future ones.
    My only problem is to allocate the storage. The iscsi device is visible to the 4 nodes.
    On one of the nodes I tried to create a new partition on the device and make the filesystem (ocfs).
    I'm using the fdisk to do the allocation, but this has a limit of <2Tera Bytes.
    Do I need to have smaller partitions and create few OVS directories ? or, is there a better way to allocate the entire space ?
    Thank you,
    Roye

    Please don't cross-post the same question in multiple forums: Re: Can a muliple OVS directories can be used when >2GB of storage is available

  • /OVS empty after upgrading to VM 2.2

    I have noticed since upgrading to VM 2.2 my /OVS directory is now empty and I have a directory /OVS.<timestamp>.bak containing all the files/directories from my VM 2.1.2 installation.
    I was managing this via Grid Control 10.2.0.5.0 but as this does not currently support VM Server 2.2 - I have installed VM Manager 2.2 with a view to creating a new Server Pool to populate /OVS
    However on doing this I got the following error -
    OVM-1011 OVM Manager communication with jalfrezi for operation HA Setup for Oracle VM Agent 2.2 failed:<Exception: Cluster root not found.>
    (or something similar)
    So the suggestion (via a few doc bugs) is to run -
    repos.py -n and repos.py -r
    To setup the Storage Repository
    When I run repos.py -n <storage> on my system
    I get a message saying something like -
    Mount point: /tmp/ovsrepos_SBkc1q
    Error: ['mount','/OVS','/tmp/ovsrepos_SBkc1q'] => mount: /OVS is not a block device
    and the same for any directory I use
    e.g.
    repos.py -n /test
    When I created this VM Server originally I used 2X250GB SATA drives as a Logical Volume (which was supported)....could this be the reason I cannot now create a storage repository now ?
    Should I re-install and just create non logical devices ?
    Thanks

    My reply may be unrelated, But I had been through the exact same situation.
    I had 4 OVM servers running 2.1.5 and later I followed Oracle recommended way (http://download.oracle.com/docs/cd/E15458_01/doc.22/e16206/toc.htm#BEJHBIIC) to upgrade them to 2.2 and post upgrade, I find that the storage is mounted under +/var/ovs/mount/uuid+ ONLY on the master pool server and rest 3 server had an empty /OVS directory.
    I tried many troubleshooting steps and have confirmed that in this scenario, restarting the "ovs-agent" service on MASTER pool server would mount the storage under +/var/ovs/mount/uuid+ on all the NON-master servers.
    To confirm this solution, I have tried upgrade process multiple times, faced exact same issue and restarting "ovs-agent" service on MASTER pool server got me going.
    --Dheeraj.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Fresh Install of VM Server Disk Storage ?

    Hi All,
    I have the following questions to the expert:
    I've installed VM Server 2.1 and I accepted the defaults. As such It used up all of my disk storage. It is my understanding that the next step (best practices) is to install the Linux Enterprise Server 5.1 . In doing so, there is one file system, I believe OVS of which I'm not certain where to install Linux OS ES 5.1.
    Then I thought that I should have customized my VM Server install disk storage. (May use logical volume management ? or just leave a reasonable amount of disk space free for the Linux Install.
    Then I thought that of removing VM Server, of which I have not found a way to remove the install of VM Server so that I could install VM Manager.
    Please explain in detail best practices for install and removal.
    Thanks

    May use logical volume management ? or just leave a reasonable amount of disk space free >>>for the Linux Install. Following Oracle VM Server release notes,You cannot set up Logical Volume Manager (LVM) during the Oracle VM Server installation.
    Workaround: Use pre-configured LVM volumes. Alternatively, you can temporarily exit the Oracle VM Server installer and create an LVM configuration from scratch. During the Oracle VM Server installation, press Alt + F2 to use the terminal, and run the lvm command. When you have finished creating the LVM configuration, press Alt + F1 to return to the Oracle VM Server installation.

  • OVM 3.3.1:  NFS storage is not available during repository creation

    Hi, I have OVM Manager  running on a separate machines managing 3 servers running OVM server  in a server pool. One of the server also exports a NFS share that all other machines are able to mount and read/write to. I want to use this NFS share to create a OVM repository but so far unable to get it to work.
    From this first screen shot we can see that the NFS file system was successfully added under storage tab and refreshed.
    https://www.dropbox.com/s/fyscj2oynud542k/Screenshot%202014-10-11%2013.40.00.png?dl=0
    But its is not available when adding a repository as shown below. What can I did to make it show up here.
    https://www.dropbox.com/s/id1eey08cdbajsg/Screenshot%202014-10-11%2013.40.19.png?dl=0
    No luck with CLI either.  Any thoughts?
    OVM> create repository name=myrepo fileSystem="share:/" sharepath=myrepo - Configurable attribute by this name can't be found.
    == NFS file system refreshed via CLI === 
    OVM> refresh fileServer name=share
    Command: refresh fileServer name=share
    Status: Success
    Time: 2014-10-11 13:28:14,811 PDT
    JobId: 1413059293069
    == file system info
    OVM> show fileServer name=share
    Command: show fileServer name=share
    Status: Success
    Time: 2014-10-11 13:28:28,770 PDT
    Data:
      FileSystem 1 = ff5d21be-906d-4388-98a2-08cb9ac59b43  [share]
      FileServer Type = Network
      Storage Plug-in = oracle.generic.NFSPlugin.GenericNFSPlugin (1.1.0)  [Oracle Generic Network File System]
      Access Host = 1.2.3.4
      Admin Server 1 = 44:45:4c:4c:46:00:10:31:80:51:c6:c0:4f:35:48:31  [dev1]
      Refresh Server 1 = 44:45:4c:4c:46:00:10:31:80:51:c6:c0:4f:35:48:31  [dev1]
      Refresh Server 2 = 44:45:4c:4c:47:00:10:31:80:51:b8:c0:4f:35:48:31  [dev2]
      Refresh Server 3 = 44:45:4c:4c:33:00:10:34:80:38:c4:c0:4f:53:4b:31  [dev3]
      UniformExports = Yes
      Id = 0004fb0000090000fb2cf8ac1968505e  [share]
      Name = share
      Description = NFS exported /dev/sda1 (427GB) on dev1
      Locked = false
    == version details ==
    OVM server:3.3.1-1065
    Agent Version:3.3.1-276.el6.7Kernel Release:3.8.13-26.4.2.el6uek.x86_64
    Oracle VM Manager
    Version: 3.3.1.1065
    Build: 20140619_1065

    Actually, OVM, as is with all virtualization servers, is usually only the head on a comprehensive infrastructure. OVM seems  quite easy from the start, but I'd suggest, that you at least skim trough the admin manual, to get some understanding of the conecpts behind it.  OVS thus usually only provides the CPU horse power, but not the storage, unless you only want to setup a single-server setup. If you plan on having a real multi-server setup, then you will need shared storage.
    The shared storage for the server pool, as well as the storage repository can be served from the same NFS server without issues. If you want to have a little testbed, then NFS is for you. It lacks some features that OCFS2 benefits from, like thin provisioning, reflinks and sparse files.
    If you want to remove the NFS storage, then you'll need to remove any remainders of any OVM object, like storage repositories or server pool filesystems. Unpresent and storage repo and delete it afterwards… Also, I hope that you didn't  create the NFS export directly on the root of the drive, since OVM wants to remove any file on the NFS export and on any root of ony volume there's the lost-found folder, which OVM, naturally, can't remove. Getting rid of such a storage repo can be a bit daunting…
    Cheers,
    budy

Maybe you are looking for