You are not logged in.
Hello, I've recently been trying to set up an NFS mount with Kerberos, however if the sec=krb5 option is present during the mount, it outputs an error. Considering this has worked in the past without issues, could this be a package regression?
mount.nfs4: timeout set for Thu Nov 30 15:09:11 2023
mount.nfs4: trying text-based options 'nfsvers=4.2,proto=tcp,sec=krb5,addr=XXX.XXX.XXX.XXX,clientaddr=XXX.XXX.XXX.XXX'
mount.nfs4: mount(2): Invalid argument
mount.nfs4: an incorrect mount option was specified for /dirI've also tried using NFSv3, but the error stays the same no matter what.
NFS server I'm connecting to is also an Arch host.
Offline
Where did you get the addr= option from? I cannot find it in the online man page.
Inofficial first vice president of the Rust Evangelism Strike Force
Online
The addr= option is automatically applied during the mount I believe. I do not have in fstab.
Offline
Update: My system was using dracut, and so I decided to boot with an mkinitcpio image. Doing so resolved the issue, leading me to believe something is wrong with the way dracut builds initramfs images.
Offline