From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>,
COMMON INTERNET FILE SYSTEM SERVER
<linux-cifsd-devel@lists.sourceforge.net>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: duplicated or invalid inode number issue with ksmbd?
Date: Tue, 18 May 2021 16:54:34 -0500 [thread overview]
Message-ID: <CAH2r5mvKvWyKdJNOuiykJKm4mS0iHpNF+n=CnmuG3H9KFq8tyA@mail.gmail.com> (raw)
Anyone see this warning (e.g. in this case running xfstest generic/013
from 5.13-rc1 to current ksmbd cifsd-for-next branch)?
[ 527.169926] run fstests generic/013 at 2021-05-18 16:50:08
[ 591.432386] CIFS: Attempting to mount \\localhost\test
[ 591.552999] CIFS: VFS: Autodisabling the use of server inode
numbers on \\localhost\test
[ 591.553017] CIFS: VFS: The server doesn't seem to support them
properly or the files might be on different servers (DFS)
[ 591.553018] CIFS: VFS: Hardlinks will not be recognized on this
mount. Consider mounting with the "noserverino" option to silence this
message.
--
Thanks,
Steve
reply other threads:[~2021-05-18 21:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH2r5mvKvWyKdJNOuiykJKm4mS0iHpNF+n=CnmuG3H9KFq8tyA@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=namjae.jeon@samsung.com \
/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).