This discussion is archived
6 Replies Latest reply: May 20, 2013 10:15 PM by Abhijit RSS

Storage refresh fails with error on OVM3.2.2

592550 Newbie
Currently Being Moderated
NFS storage refresh job on OVMM 3.2.2 fails with following error, any tips?

Job Construction Phase
----------------------
Job ID: 1363980185550

begin()
com.oracle.odof.exception.ObjectException: Caught during invoke method: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_2005E "0004fb0000090000db92280209a5ce3c (rstnlin204-nfs)" contains a component "0004fb0000090000db92280209a5ce3c" in error. Error event: StatusEvent (03/22/2013 10:22:00:075 AM), Summary: File Server Has Invalid Exports [Fri Mar 22 15:23:05 EDT 2013]
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:880)
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.storage.Transaction.processCommand(Transaction.java:601)
at com.oracle.odof.core.TransactionManager.processTransactionWork(TransactionManager.java:651)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:756)
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_2005E "0004fb0000090000db92280209a5ce3c (rstnlin204-nfs)" contains a component "0004fb0000090000db92280209a5ce3c" in error. Error event: StatusEvent (03/22/2013 10:22:00:075 AM), Summary: File Server Has Invalid Exports [Fri Mar 22 15:23:05 EDT 2013]
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.validateOperation(ManagedObjectDbImpl.java:118)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.addJobOperationAtIndex(ManagedObjectDbImpl.java:1340)
at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.addJobOperation(ManagedObjectDbImpl.java:1393)
at com.oracle.ovm.mgr.api.physical.storage.FileServerDbImpl.refresh(FileServerDbImpl.java:318)
at com.oracle.ovm.mgr.api.physical.storage.FileServerDbImpl.refresh(FileServerDbImpl.java:282)
at com.oracle.ovm.mgr.api.physical.storage.FileServerDbImpl.refresh(FileServerDbImpl.java:267)
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)
... 9 more

Job Aborted from server, cleaning up client.

Thank you.
  • 1. Re: Storage refresh fails with error on OVM3.2.2
    592550 Newbie
    Currently Being Moderated
    UPDATE: I found what causes it but don't know how to fix it, any ideas ?

    The NFS server which hosts my OVM repository also has other shares that is used by other applications. One of the other shares were removed and nfs was refreshed by NFS administrator. OVM is stuck on this and still showing the removed share under storage file system. I acknowledged the message but it still show red icon on this storage and the refreshes fail with above message. Does any one know how to clear this situation?

    Thanks.
  • 2. Re: Storage refresh fails with error on OVM3.2.2
    592550 Newbie
    Currently Being Moderated
    more UPDATE: I finally found the event:

    Description: OVMEVT_00A005D_000 File Server: <file-server>, has invalid exports.
    Export: /U02, is contained in export: /U02/grc1. Remove one of those exports on the file server,
    and then refresh the file server to clear the error.

    The invalid export (U02) has been removed since, and the event has been acknowledged, showmount on the server shows correct mounts too, but OVM refresh still fails with above messages. It looks like the OVM is not aware of the new and corrected exports. I even restarted ovmm service too.

    Any way to clear this?
  • 3. Re: Storage refresh fails with error on OVM3.2.2
    592550 Newbie
    Currently Being Moderated
    more detail, found this on known Limitations and workarounds in Release notes for OVM 3.2.1

    8.5.11. Refreshing a NAS-based File System Produces Invalid/Overlapping Exports

    When a NAS-based file system is refreshed, it may produce invalid or overlapping exports. During a file system refresh job, all mount points defined in the NAS-based file server's exports file are refreshed, even file systems that are not intended to be used in Oracle VM environments.

    Top level directories which also contain subdirectories in the exports file may also cause problems, for example, if an export file contains /xyz as an export location, and also contains /xyz/abc. In this case, the following error may be displayed during a refresh file system job:

    OVMRU_002024E Cannot perform operation. File Server: server_name, has invalid exports.

    Workaround: For the second issue, to work around this problem, do not export top level file systems in the NAS-based file server's exports file.

    Bug 12800760
    #

    I have tried this workaround, but it doesn't seem to work, I can not find the bug on my oracle support bug database either. I hope some one has tried something that worked..., please let me know if you do.

    Thanks.
  • 4. Re: Storage refresh fails with error on OVM3.2.2
    Abhijit Newbie
    Currently Being Moderated
    ^^ So, did you find a resolution to this problem? I am facing similar issues. And, i am adding a new Repository (Discover File Server).

    I tried mounting just the desired nfs mountpoint on all the servers, same error. Also tried mounting all the discovered nfs shares, same error.

         

    OVMAPI_2005E "0004fb0000090000f84270b6d3a90601 (OVM_NFS_VOL1)" contains a component "0004fb0000090000f84270b6d3a90601" in error. Error event: StatusEvent (03/12/2013 02:42:14:958 PM), Summary: File Server Has Invalid Exports [Tue Mar 12 14:46:47 PDT 2013]
  • 5. Re: Storage refresh fails with error on OVM3.2.2
    user12273962 Pro
    Currently Being Moderated
    So you don't have top level shares? There should no shares above the NFS shares you are mounting for storage repos.
  • 6. Re: Storage refresh fails with error on OVM3.2.2
    Abhijit Newbie
    Currently Being Moderated
    ^^ Ya, that was the issue.

    Cannot have parent level exports when child level exports exist. Had Storage guy block access to the offending parents.

    Here is the support article where this issue has been discussed : https://support.oracle.com/epmos/faces/DocumentDisplay?id=1437493.1

    Problem Resolved !

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points