You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When number of files on the host on single directory level is bigger than 128, there is no access to that directory is on mounted volume in minikube.
What you expected to happen:
Have an access to the directories with number of files limited by filesystem or at least much bigger than 128
How to reproduce it (as minimally and precisely as possible):
$> mkdir -p /tmp/k8s-volume/vvv; rm -rf /tmp/k8s-volume/vvv/*; for ii in {0..129}; do touch /tmp/k8s-volume/vvv/$ii; done
$> minikube mount /tmp/k8s-volume/vvv:/vvv&
This daemon process needs to stay alive for the mount to still be accessible...
ufs starting
$> minikube ssh "ls -l /vvv"
total 0
ls: reading directory '/vvv': Unknown error 526
E0725 17:11:19.411816 6961 ssh.go:53] Error attempting to ssh/run-ssh-command: exit status 2
The text was updated successfully, but these errors were encountered:
If you upgrade to the latest release of minikube v0.21.0 this should be fixable now. In this release, there is now an --msize flag that you can configure. The default value has been doubled be 262144 in the new release which should allow for your dir size. If you are still seeing this issue, pass in a larger value for the msize and rerun mount: minikube mount --msize=524288
BUG REPORT
Minikube version:
v0.20.0
Environment:
What happened:
When number of files on the host on single directory level is bigger than 128, there is no access to that directory is on mounted volume in minikube.
What you expected to happen:
Have an access to the directories with number of files limited by filesystem or at least much bigger than 128
How to reproduce it (as minimally and precisely as possible):
$> mkdir -p /tmp/k8s-volume/vvv; rm -rf /tmp/k8s-volume/vvv/*; for ii in {0..129}; do touch /tmp/k8s-volume/vvv/$ii; done
$> minikube mount /tmp/k8s-volume/vvv:/vvv&
This daemon process needs to stay alive for the mount to still be accessible...
ufs starting
$> minikube ssh "ls -l /vvv"
total 0
ls: reading directory '/vvv': Unknown error 526
E0725 17:11:19.411816 6961 ssh.go:53] Error attempting to ssh/run-ssh-command: exit status 2
The text was updated successfully, but these errors were encountered: