From: Orion Poplawski <orion@nwra.com>
To: linux-cifs@vger.kernel.org
Subject: User loosing access to cifs mount
Date: Wed, 1 Jun 2022 10:17:20 -0600 [thread overview]
Message-ID: <c0c6d353-5868-01bb-8139-331bcf3e5782@nwra.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
We're using multiuser automounted cifs mounts. Generally works fine, but
sometimes a user looses access:
$ klist
Ticket cache: KEYRING:persistent:XXXX:krb_ccache_pPI2o2r
Default principal: user@REALM
Valid starting Expires Service principal
06/01/2022 08:53:25 06/01/2022 18:08:51 cifs/server@REALM
renew until 06/07/2022 17:49:23
06/01/2022 08:08:51 06/01/2022 18:08:51 krbtgt/REALM@REALM
renew until 06/07/2022 17:49:23
$ ls -la /nwra/monterey/csp/
ls: cannot access '/nwra/monterey/csp/': Permission denied
mount shows:
//SERVER/csp on /nwra/monterey/csp type cifs
(rw,relatime,vers=3.1.1,sec=krb5,cruid=XXXX,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=XXXX,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,noperm,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=15)
The cruid is the id of the user without access. Another user of the system
does have access.
Fedora 34 - 5.17.5-100.fc34.x86_64
If the directory unmounts and gets remounted then access is restored.
Any idea what to test and how to debug?
Thanks!
--
Orion Poplawski
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@nwra.com
Boulder, CO 80301 https://www.nwra.com/
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3847 bytes --]
reply other threads:[~2022-06-01 16:17 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=c0c6d353-5868-01bb-8139-331bcf3e5782@nwra.com \
--to=orion@nwra.com \
--cc=linux-cifs@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