From: Matt <matt.w.burnett-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: MS SOFS compatibility issue
Date: Thu, 30 Nov 2017 21:55:06 -0600 [thread overview]
Message-ID: <2E12F6EE-3C29-4C03-B3F4-822FBB98AC10@gmail.com> (raw)
In-Reply-To: <FB50F504-E400-44E8-904F-528E345C1AEE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Sorry, I forgot to subscribe to this list, if you replied, and did not include me directly, if you could resend your message to me, I’d appreciate it.
On 11/30/17, 4:31 PM, "Matt" <matt.w.burnett-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
I’ve been experiencing issues when trying to mount CIFS shares on a Microsoft Scale Out File Server 2016 Cluster from a VMware Photon Linux 1.0 client. If a vers option is not provided, mount.cifs will give the error mount error(13): Permission denied. I was able to work around them by specifying vers=3.02 as a mount option, but a kernel update eventually broke that and I was forced to use vers=2.0. However since upgrading to Photon 2.0, the mount.cifs version changed from 6.4 to 6.7, and whenever I specify a vers= option, it gives the error mount error(22): Invalid argument. If it is relevant the Photon 1.0 client was running kernel 4.4.96-1 and Photon 2.0 is running kernel 4.9.60-1.
Does anyone know what I can do to resolve these issues? Can someone point me in the direction of where I should submit a bug report? Thanks!
prev parent reply other threads:[~2017-12-01 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 22:31 MS SOFS compatibility issue Matt
[not found] ` <FB50F504-E400-44E8-904F-528E345C1AEE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-01 3:55 ` Matt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2E12F6EE-3C29-4C03-B3F4-822FBB98AC10@gmail.com \
--to=matt.w.burnett-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox