From 609f83b69e43992de409a73d28c9e75f98f72bb0 Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Thu, 24 Dec 2015 12:48:32 -0800 Subject: [PATCH] website/docs: document workaround for SMB bad fs type [GH-6704] --- .../docs/source/v2/synced-folders/smb.html.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/website/docs/source/v2/synced-folders/smb.html.md b/website/docs/source/v2/synced-folders/smb.html.md index 65d679794..5b78153ee 100644 --- a/website/docs/source/v2/synced-folders/smb.html.md +++ b/website/docs/source/v2/synced-folders/smb.html.md @@ -84,3 +84,25 @@ never pruned or cleaned up. Once the folder share is defined, Vagrant never removes it. To clean up SMB synced folder shares, periodically run `net share` in a command prompt, find the shares you don't want, then run `net share NAME /delete` for each, where NAME is the name of the share. + +## Common Issues + +### "wrong fs type" Error + +If during mounting on Linux you're seeing an error message that includes +the words "wrong fs type," this is because the SMB kernel extension needs to +be updated in the OS. + +If updating the kernel extension is not an option, you can workaround the +issue by specifying the following options on your synced folder: + +
+mount_options: ["username=USERNAME","password=PASSWORD"]
+
+ +Replace "USERNAME" and "PASSWORD" with your SMB username and password. + +Vagrant 1.8 changed SMB mounting to use the more secure credential file +mechanism. However, many operating systems ship with an outdated filesystem +type for SMB out of the box which doesn't support this. The above workaround +reverts Vagrant to the insecure before, but causes it work.