Unexpected Stale NFS file handle errors on NetBSD client #34
Labels
Comments
|
Thank you for your report. I don't know if anyone has time to look at it right away, but do you think you could get a network dump using tcpdump and attach it here? |
|
Here is a tcpdump log on Ubuntu unfs3 server (192.168.20.204) and NetBSD client (192.168.20.1) with the following commands: |
|
Hi @tsutsui , @CendioOssman ! But you've got the problem on docker. Lets try this too(on SSH port 22222): More questions than answers... Also, somehow this works for mister |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
docker-netbsd uses unfs3 0.9.22 built for docker-alpine 3.16.
When I tried this docker-netbsd image on ubuntu 22.04.2 LTS, several build operations triggers NFS errors.
This also happens with unfs3 0.10.0 on a ubuntu 22.04.2 server and a NetBSD client on real machines.
On the other hand, these errors don't occur if a file system on the ubuntu server is converted from ext4 to btrfs.
The following procedure can reproduce this problem
sudo docker pull madworx/netbsd:latestsudo docker run --rm -d --device=/dev/kvm -e "SSH_PUBKEY=$(cat ~/.ssh/id_rsa.pub)" -p 2222:22 --name netbsd madworx/netbsd:latestssh -p 2222 root@localhostcd /tmp; mkdir a; rmdir a; touch a; rm a; rmdir aI've also created updated docker-netbsd images that use the latest ufs3 0.10.0 on alpine linux but this can still be reproducible.
The text was updated successfully, but these errors were encountered: