Restore mount command and unswap port and mountVersion

[q3aiml]

@aaron-prindle this seems to have been a mistake in 6f42d58 (#1705)?

[minikube-bot]

Can one of the admins verify this patch?

[codecov-io]

Codecov Report

Merging #1717 into master will increase coverage by 0.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1717      +/-   ##
==========================================
+ Coverage   35.93%   35.94%   +0.01%     
==========================================
  Files          51       51              
  Lines        3337     3338       +1     
==========================================
+ Hits         1199     1200       +1     
  Misses       1958     1958              
  Partials      180      180

Impacted Files	Coverage Δ
pkg/minikube/cluster/cluster.go	41.12% <0%> (ø)	⬆️
cmd/minikube/cmd/mount.go	8.24% <100%> (+0.95%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9e8ef22...1f1076d. Read the comment docs.

[dlorenc]

@minikube-bot ok to test

[q3aiml]

I'm running into one other issue after 6f42d58 where it seems the port and version are swapped:

sudo mount -t 9p -o trans=tcp,port=9p2000.u,dfltuid=1001,dfltgid=1001,version=32777,msize=262144 192.168.42.1 /opt/host-persist;
    sudo chmod 775 /opt/host-persist;
    SSH cmd err, output: <nil>: mount: wrong fs type, bad option, bad superblock on 192.168.42.1,

Let me know if it is better to add that change here or open a separate PR.

[aaron-prindle]

@q3aiml Thanks for catching this! If you can put the port/version change in this PR that would be great, thanks!

[q3aiml]

Sure thing! Thank you for digging into the 9p issues. It's the best after hitting an issue to go and find that not only do others see it too (I'm not alone!) but then there is also a patch