Double entries in /etc/exports #4666
Comments
|
I experienced this problem again this morning, the relevant output of I checked this against a |
|
This also happens to me, on Gentoo. Every time vagrant duplicates the export entries |
|
This has been an intermittent issue for me as well, was actually about to file this one yesterday. It's gone from 2x > normal behavior > 2x > 4x. |
|
This is most probably caused by #5957 - /etc/exports isn't being overwritten by the cleaned-up file, because "cp" lacks sudo permissions, causing the file being cluttered with the same entries. |
|
I'm not sure @artjomsimon's diagnosis is 100% right. I'm running 1.7.4 -- which includes the fix for #5957 -- and still experiencing this issue. |
|
What the proper workaround? Manually remove vagrant entries from |
|
This seems to be happening to me on a multi-machine setup. I'm sharing the same folder with both machines so I'm getting the same export twice (once per IP address). |
|
Still the same problem. I have only one machine now, others already cleaned. and after --debug: |
|
Any workaround? I tried manually editing /etc/exports with no luck. Might be a coincidence, but I'm also using geerlingguy/ubuntu1604 box. |
|
FWIW, this problem usually happens to me when I have two |
|
@arturolinares I'm having the same issue. Did you find a workaround? |
|
Not really. I reinstalled vagrant and the error was still there, but the VM was functional.
De: Patrick Coffey <[email protected]>
Responder a: mitchellh/vagrant <[email protected]>
Fecha: martes, 13 de junio de 2017, 10:56
Para: mitchellh/vagrant <[email protected]>
CC: Arturo Linares Goenaga <[email protected]>, Mention <[email protected]>
Asunto: Re: [mitchellh/vagrant] Double entries in /etc/exports (#4666)
@arturolinares<https://github.com/arturolinares> I'm having the same issue. Did you find a workaround?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#4666 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAMZRuDIhIoYBI1JYCsV8k8RGXKc5Glrks5sDrEcgaJpZM4CwitT>.
|
|
Hello, I'm having this issue in Fedora. What's the status? |
|
I believe I'm having the same issue when trying to "vagrant up". I can't run nfs-server.service manually either, it fails with the same I've removed the duplicated lines from /etc/exports, destroyed the vagrant vm, to vagrant up again only to have it put more duplicates in. Not sure whats going on.. I'm at the end of my rope. Any help on this would be much appreciated! I'm running Antegos Linux. |
|
For me, double entries appear in NOTE: If I'm adding three mount points for the same directory, it appears three times in Looking at the issue description and comments, you guys might have the same problem as me. Could you please check if the path in |
|
The code responsible for this issue is in plugins/hosts/linux/cap/nfs.rb. The EDIT: Actually, I believe that |
briancain
added a commit
to briancain/vagrant
that referenced
this issue
Sep 5, 2017
…exports Prior to this commit, if you set up multiple folders to export with NFS on linux with the exact same hostpath, the template used to write /etc/exports would end up placing the same path with the same IP in /etc/exports and cause an error preventing the folders from being properly mounted. This commit fixes that by first looking at which folders are being exported and if there are any duplicates. If so, remove the duplicates and only export 1 hostpath folder. If these duplicate folders have differing nfs linux options, an exception must be thrown because we cannot assume which options the user intended to export with.
|
Thanks so much for bringing this up @SchnWalter . I was finally able to reproduce this bug based on your comments above. I've opened #8945 to fix this bug. |
briancain
added a commit
to briancain/vagrant
that referenced
this issue
Sep 5, 2017
…exports Prior to this commit, if you set up multiple folders to export with NFS on linux with the exact same hostpath, the template used to write /etc/exports would end up placing the same path with the same IP in /etc/exports and cause an error preventing the folders from being properly mounted. This commit fixes that by first looking at which folders are being exported and if there are any duplicates. If so, remove the duplicates and only export 1 hostpath folder. If these duplicate folders have differing nfs linux options, an exception must be thrown because we cannot assume which options the user intended to export with.
k-oguma
pushed a commit
to k-oguma/vagrant
that referenced
this issue
Nov 9, 2017
…exports Prior to this commit, if you set up multiple folders to export with NFS on linux with the exact same hostpath, the template used to write /etc/exports would end up placing the same path with the same IP in /etc/exports and cause an error preventing the folders from being properly mounted. This commit fixes that by first looking at which folders are being exported and if there are any duplicates. If so, remove the duplicates and only export 1 hostpath folder. If these duplicate folders have differing nfs linux options, an exception must be thrown because we cannot assume which options the user intended to export with.
|
Here is the patch for vagrant-1.9.1 shipped with Fedora 26, to apply: |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sometimes Vagrant puts doubles entries in
/etc/exports, causing nfsd to fail, for example:I have this maybe once every two weeks, for all projects (using Vagrant daily).
I've been getting in the habit of using
vagrant up --debug, but for some reason the problem only seems to occur if I leave the--debugflag out (probably coincidence, since sometimes I forget), so I can't point you to the cause of these problems...I'm using Vagrant 1.6.5 on Arch Linux. I also had this problem on Ubuntu 12.04, and has been around since at least March (since I've been using Vagrant).
The text was updated successfully, but these errors were encountered: