Public bug reported:
Some of our build machines have recently started failing builds. It was
noted that all the machines that fail the build are running the most
recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu.
The following command was created to minimally reproduce the issue:
$ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk
| tee -a /tmp/ls.log 2>&1; sleep 1;done
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
Note directly trying to list the file works every time, it seems the bug must
be related to the use of the wildcard.
$ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
| tee -a /tmp/ls.log 2>&1; sleep 1;done
-rw-r--r-- 1 jenkins engineer 202526 May 2 13:47
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
-rw-r--r-- 1 jenkins engineer 202526 May 2 13:47
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
-rw-r--r-- 1 jenkins engineer 202526 May 2 13:47
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
The drop_cache was needed to force the error everytime, otherwise it
would fail only a few times then succeed a bunch in a row before
randomly failing again.
$ cat /usr/local/scripts/drop_cache.sh
#!/bin/bash
# Test script to drop filesystem cache
sync
# Clear pagecache, dentries, and inodes
echo 3 > /proc/sys/vm/drop_caches
Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the
problem to go away.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174
Uname: Linux 5.4.0-107-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
Date: Tue May 3 15:04:34 2022
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-signed-hwe-5.4 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482
Title:
nfs cannot access/list wildcard file unless its cached
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
