#4142 NFS Mount Error

1.590
closed-fixed
5
2013-08-27
2012-09-16
markITman
No

I am unable to mount NFS drives either using version 3 or 4 with the latest webmin. I have Three ubuntu systems 2 of which have 10.04 and one 12.04. The problem tracks the webmin version.
ERROR MESSAGE "Failed to save mount : '/home/mark/Downloads' is not a valid directory name. The available directories on myth4.local are :
/export
/home/mark/Downloads"

You get the above error where it says the directory you want to mount is not valid and it lists valid directoriies. As you can see the directory that is indicated as not valid is in the list of valid directories.

I verified that this is a problem with this version of webmin by using one of my computers with webmin version1.540 and can mount this drive no problem.

So to summarize, Mount problems occure with webmin version 1.590 using Ubuntu 12.04 or 10.04. It works correctly with version 1.540 on ubuntu 10.04.

Discussion

  • sdaau

    sdaau - 2013-08-26

    Hi, I just experienced the same problem. Looking through the code, that error message is defined as save_edirname (in webmin/mount/lang/en); and it appears to be triggered in webmin/mount/save_mount.cgi, by failing the check if (@access_fs && $in{directory}); so apparently this is due to access rights.

    I'm using a similar setup, where I tried webmin_1.580_all.deb on Ubuntu 11.04 machine as server - and Ubuntu 12.04 machine as client; and the client had the same problem as described. I originally thought I was doing an NFS v4 export on server, and I tried to access via NFS v4 on client - which is what got me the error.

    Looking further into this, it turns out when I do Networking/NFS Exports/Add a new export on the server, and choose NFS v4 version from there, and accept the default "NFSv4 Pseudofilesystem to export" as /export, and Save after entering all other info - then, when trying to browse the saved export, it turns out it is set to nfs 3 anyways (and there is no pseudofilesystem), Knowing this, when I try the mount from client as NFS v3, it ended up working for me - which is a bit better than the state described in the #4142 bug (where there is a "problem either using version 3 or 4"). Anyways, hope this may help someone...

     
  • Jamie Cameron

    Jamie Cameron - 2013-08-26

    This will be fixed in the next Webmin release.

     
  • Jamie Cameron

    Jamie Cameron - 2013-08-26
    • labels: Disk and Network
      Filesystems --> Disk and Network Filesystems
    • status: open --> closed-fixed
     
  • sdaau

    sdaau - 2013-08-27

    Hi all,

    Stop the presses :) - and disregard my previous comment, it seems I was wrong...

    I just wanted to say that I did a test run again, on the same machines where I got this error - and it looks like there is nothing to fix; it looks like all is working. I documented that in this post:

    linux - NFS Server/Client administration of multiple machines - Super User

    I used Ubuntu 11.04 and Ubuntu 12.04, corresponding dependencies and again webmin 1.580 .deb. For the server side, I think one of the problems is Webmin / Bugs / #4286 NFS v4 exports do not persist as v4 upon edit - they revert to v3; and NFS Version help missing, as it makes someone who doesn't really know NFS (like me) rather confused on whether v3 or v4 is being used - but that is obvious only if you edit the NFS exports once added. Otherwise, if you just add one NFSv4 export after a fresh install, and change your options during the add, and then accept the defaults - then all seems to work fine.

    For the client side, I am pretty sure that when I got the "Failed to save mount : '/...' is not a valid directory name" error, what I did was click on /export, and after it failed, then on the /export/subdir. I completely missed the text on that window, that says:

    For an NFSv4 mount, you should select '/'

    So in the test in the post above - that is what I did: I clicked on /, and everything works fine. And if one also remembers chmod 777 of the export directory on the server side - then writing from the client side works too.

    So, just wanted to say, that my previous comment is deprecated - though I'm not sure if my situation is exactly the same as the one in the original bug post. Still, it looks to me like there is probably nothing to fix - if one should choose the / for NFSv4, then I guess if you try anything else, "not a valid directory name" is a proper error response.

    Hope this helps,
    Cheers!

     
  • Jamie Cameron

    Jamie Cameron - 2013-08-27

    Ok, thanks for the update! I added code to check if the path entered is in the list of those exported, and always accept it if so.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks