Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #81237
| From | Dietrich Clauss <dietrich@clauss-it.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#880549: NFSv4 broken / nfs v4.1 lock problems |
| Date | 2023-12-18 15:00 +0100 |
| Message-ID | <HMmk1-eqta-5@gated-at.bofh.it> (permalink) |
| References | <uHfiF-25A-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
In Bookworm I no longer see the "lock reclaim failed" errors.
Further investigation revealed that the affected installations were also
affected by five-second delays as described here
<https://lore.kernel.org/linux-nfs/59682160-a246-395a-9486-9bbf11686740@mathematik.uni-wuerzburg.de/>.
These show similar symptoms and they also occur on nfs v4.{1,2} only.
So I had to change the lines in <etc/exports> from
| /srv/nfs gss/krb5p(rw,fsid=0,crossmnt,no_subtree_check)
to
| /srv/nfs *(sec=krb5p,rw,fsid=0,crossmnt,no_subtree_check)
Done that and everything runs fine.
In my experience the bug report can be closed.
Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread
Bug#880549: NFSv4 broken / nfs v4.1 lock problems Dietrich Clauss <dietrich@clauss-it.com> - 2023-12-18 15:00 +0100
csiph-web