linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: L Walsh <cifs@tlinx.org>
To: linux-cifs <linux-cifs@vger.kernel.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Regression -- linux 5.5.3: can no longer mount with unix extentions using cifs 2.1 (Win10-only client additions)
Date: Sat, 22 Feb 2020 17:52:42 -0800	[thread overview]
Message-ID: <5E51DAEA.8090702@tlinx.org> (raw)

hard links and serverino numbers, among other things used to work when
mounting a win7 client using a linux cifs client

I tried this today, and am getting:

[701913.978407] CIFS VFS: Autodisabling the use of server inode numbers 
on \\Athenae\C.
[701913.986151] CIFS VFS: The server doesn't seem to support them 
properly or the files might be on different servers (DFS).
[701913.997116] CIFS VFS: Hardlinks will not be recognized on this 
mount. Consider mounting with the "noserverino" option to silence this 
message.
[703793.287615] CIFS VFS: Server does not support mounting with posix 
SMB3.11 extensions.
[703793.295810] CIFS VFS: cifs_mount failed w/return code = -95

The win7 workstation in question is running 1 hard disk, no DFS.

Unix extensions worked long before SMB3.x.  It seems there is ongoing work
to disable SMB2.1 support and replace it with only latest SMB from MS
compatible with Win10. 

If MS wants to backport SMB3.x to Win7, that would be fine, but I
doubt that is going to happen.  NTL, if they keep breaking 2.1 compatibility
that would be one option.




             reply	other threads:[~2020-02-23  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23  1:52 L Walsh [this message]
     [not found] ` <CAH2r5mtNgEi1noHAY0v_LmnwFOOZ1LsQ20zwTwWNk4uL5HY3EA@mail.gmail.com>
2020-02-24  1:59   ` Regression -- linux 5.5.3: can no longer mount with unix extentions using cifs 2.1 (Win10-only client additions) L Walsh
2020-02-24  6:05     ` Steve French
2020-02-24 11:05 ` Aurélien Aptel

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=5E51DAEA.8090702@tlinx.org \
    --to=cifs@tlinx.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).