-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rm -rf failed with "Directory not empty" #1274
Comments
@vibhansa-msft @souravgupta-msft could you take a look at this issue? thanks. |
@andyzhangx , @vibhansa-msft @souravgupta-msft, any update for this issue? |
Hi @tanvp112, this is a bug in the file cache mode. We will fix this in our next release. |
@souravgupta-msft so |
Yes, file cache is default. This issue is with file cache where local cached directory is not getting renamed. You can use block cache to mitigate this. Let us know if the issue persists in block cache. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What happened:
Create PVC and pod as usual:
Exec into the pod and make changes:
While the
mv
command did not report any failure, but the log on the node has shown:Now perform
rm -rf /test/*
will fail withrm: can't remove 'one': Directory not empty
.Check using
ls -a /test/one
and on the Portal, both ways shown theone
directory has no object in it.Now perform
mv /test/one /test/two
and follow byrm -rf /test/*
the command succeeded!!Repeat the test commands above again and the result is repeating.
What you expected to happen:
mv
andrm -rf
command should just work and the fuse log should be free of error.How to reproduce it:
See above.
Anything else we need to know?:
IMPORTANT Use a new StorageClass with
--use-adls=true
withisHnsEnabled: "true"
yield the same outcome.Environment:
kubectl version
): 1.27.9uname -a
): Linux aks-system-31080464-vmss000000 5.15.0-1056-azureThe text was updated successfully, but these errors were encountered: