From: Anthony Joseph Messina <amessina@messinet.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFS client cannot "see" files or directories in /home/<username>
Date: Sun, 13 Sep 2020 12:22:25 -0500 [thread overview]
Message-ID: <5949391.lOV4Wx5bFT@linux-ws1.messinet.com> (raw)
In-Reply-To: <12603973.uLZWGnKmhe@linux-ws1.messinet.com>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
On Saturday, August 29, 2020 5:52:19 PM CDT Anthony Joseph Messina wrote:
> I've reported this issue to Fedora:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/
> thread/YECR5Q4LLTEQO3RNSXXKOCZUZF53UAST/
> https://bugzilla.redhat.com/show_bug.cgi?id=1873720
>
> I've got an NFS client that mounts /home via NFSv4.2 with sec=krb5p. Any
> kernel since 5.7.17 through 5.8.4 is unable to "see" files or directories in
> the mounted /home/<username> directory with the exception of the first
> "dot" directory.
>
> While I cannot see /home/<username>/subdirectory, if I manually cd into
> /home/ <username>/subdirectory, I can list that subdirectory's contents as
> normal.
>
> If I mv "/home/<username>/.dotdir" to "/home/<username>/.dotdir.old", I can
> no longer see it, and I can see "/home/<username>/.dotnextdir".
>
> If I then mv "/home/<username>/.dotdir.old" back to "/home/
> <username>/.dotdir", I am not able to see it and can still only see "/home/
> <username>/.dotnextdir"
>
> My last NFS client that can "see" /home/<username> directory contents
> (normal operation) is kernel-5.7.15 (I was unable to test 5.7.16)
>
> NFS server upgrades from kernel-5.7.15 through kernel-5.8.4 didn't seem to
> have any affect.
>
> I understand this list is for developers, but I'm wondering if any of the
> NFS experts can point me in the right direction... Thank you.
The Fedora bugzilla provides additional information:
In https://bugzilla.redhat.com/show_bug.cgi?id=1873720#c7 a user reports the commit that creates the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b4487b93545214a9db8cbf32e86411677b0cca21
In https://bugzilla.redhat.com/show_bug.cgi?id=1873720#c12 another user reports the relationship with exports using the "security_label" option
--
Anthony - https://messinet.com
F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-13 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 22:52 NFS client cannot "see" files or directories in /home/<username> Anthony Joseph Messina
2020-09-13 17:22 ` Anthony Joseph Messina [this message]
2020-09-19 0:14 ` Anthony Joseph Messina
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=5949391.lOV4Wx5bFT@linux-ws1.messinet.com \
--to=amessina@messinet.com \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.