Unable to delete NFS share

  • I get the following error when trying to delete NFS share. Only one share gets the error. the others deleted without any problems.
    The best I can tell there was no entry created in /etc/fstab for this share
    I manually created an entry for it in /etc/exports and a bind in /etc/fstab and it exports and mounts to the client


    I think the error may actually have occured when I created it. Is there someway of manually deleting it from the "Web administration Interface"?



    Failed to get configuration (xpath=//system/fstab/mntent[uuid='6cc0f456-469a-4c50-b996-e753b1a73ef0'])


    Error #3003:
    exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[uuid='6cc0f456-469a-4c50-b996-e753b1a73ef0'])' in /var/www/openmediavault/module/nfs.inc:95
    Stack trace:
    #0 [internal function]: NFSModule->preDeleteShare(Array)
    #1 /usr/share/php/openmediavault/notify.inc(123): call_user_func_array(Array, Array)
    #2 /var/www/openmediavault/rpc/nfs.inc(347): OMVNotifyDispatcher->notify(16, 'org.openmediava...', Array)
    #3 [internal function]: NFSRpc->deleteShare(Array)
    #4 /usr/share/php/openmediavault/rpc.inc(261): call_user_func_array(Array, Array)
    #5 /usr/share/php/openmediavault/rpc.inc(97): OMVRpc::exec('NFS', 'deleteShare', Array)
    #6 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
    #7 {main}

  • I've figured out how to remove NFS entries from the "Web administration Interface" that fail when trying to delete. To fix the problem will require you to manually edit config.xml


    Some history:
    The first time I tried to create an NFS share for one of my sub-directories it did not work correctly. The other share creations were ok. It failed even though it did not indicate an error had occurred. The entry was correct in the config.xml file but failed to create bind entries in the /etc/fstab for this share.


    There were several times (there after) that it failed to write the correct info. Once I figured out how to remove the shares config.xml file the second attempt worked perfectly.


    There is, I do believe, a bug in the script that creates these entries in the various files.







    # this is the NFS excerpt from my /etc/openmediavault/config.xml file
    <nfs>
    <enable>1</enable>
    <numproc>8</numproc>
    <shares>
    <share>
    <uuid>23aaa89e-d25c-450f-a75a-b439edfe3527</uuid>
    <sharedfolderref>0b6ece8f-4c68-49d7-ad66-c637b8df19f3</sharedfolderref>
    <mntentref>7de2f486-7927-4475-873b-99aa2396b249</mntentref>
    <client>192.168.1.0/24</client>
    <options>ro</options>
    <extraoptions>subtree_check,secure</extraoptions>
    <comment>Windows XP</comment>
    </share>
    <share>
    <uuid>478ebe66-c6ef-4460-8f22-b4e5e301fed2</uuid>
    <sharedfolderref>b8b2d580-e391-4600-828e-ada501e195d9</sharedfolderref>
    <mntentref>a0066c13-9434-4781-8f3e-3c0b1a806a26</mntentref>
    <client>192.168.1.0/24</client>
    <options>rw</options>
    <extraoptions>subtree_check,secure</extraoptions>
    <comment>WD320G root</comment>
    </share>
    <share>
    <uuid>63eb339c-037f-4fc5-99f5-218e637861e7</uuid>
    <sharedfolderref>f683e9b1-687d-4ac1-837e-057f4f221aec</sharedfolderref>
    <mntentref>e1099735-ad7a-4038-a7f7-2868d63a069e</mntentref>
    <client>192.168.1.0/24</client>
    <options>ro</options>
    <extraoptions>subtree_check,secure</extraoptions>
    <comment>LinuxMint11 root read only</comment>
    </share>
    <share>
    <uuid>07717f31-e841-4275-ac70-d9dc635a28f1</uuid>
    <sharedfolderref>2ca3404d-ece2-4f4d-8b24-c30342d6e0bb</sharedfolderref>
    <mntentref>cc310255-ec0b-4934-a3cc-015ae70299a0</mntentref>
    <client>192.168.1.0/24</client>
    <options>rw</options>
    <extraoptions>subtree_check,secure</extraoptions>
    <comment>LM11 Downloads directory</comment>
    </share>
    </shares>client

  • Thanks for this, I've had thsi issue for a while but haven't had time to find a solution.


    I think it was caused by some white space in the permission box. The ones I can't delete have subtree_check, secure rather than subtree_check,secure.



    Cheers

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!