-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
"Must-remove" files cannot be removed because "file exists" #6396
Labels
bug
Something isn't working
Comments
related #162 |
hagen1778
pushed a commit
to pludov/VictoriaMetrics
that referenced
this issue
Jun 4, 2024
hagen1778
added a commit
that referenced
this issue
Jun 4, 2024
…TEMPTY (#6398) ### Describe Your Changes Fix for issue #6396: according to rmdir manpage, ENOTEMPTY and EEXIST should be treated equally #6396 ### Checklist The following checks are **mandatory**: - [x ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Co-authored-by: Ludovic Pollet <ludovic.pollet@exfo.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
hagen1778
pushed a commit
that referenced
this issue
Jun 4, 2024
…TEMPTY (#6398) ### Describe Your Changes Fix for issue #6396: according to rmdir manpage, ENOTEMPTY and EEXIST should be treated equally #6396 ### Checklist The following checks are **mandatory**: - [x ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Co-authored-by: Ludovic Pollet <ludovic.pollet@exfo.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3ddae77)
hagen1778
pushed a commit
that referenced
this issue
Jun 4, 2024
…TEMPTY (#6398) ### Describe Your Changes Fix for issue #6396: according to rmdir manpage, ENOTEMPTY and EEXIST should be treated equally #6396 ### Checklist The following checks are **mandatory**: - [x ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Co-authored-by: Ludovic Pollet <ludovic.pollet@exfo.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3ddae77)
hagen1778
pushed a commit
that referenced
this issue
Jun 4, 2024
…TEMPTY (#6398) ### Describe Your Changes Fix for issue #6396: according to rmdir manpage, ENOTEMPTY and EEXIST should be treated equally #6396 ### Checklist The following checks are **mandatory**: - [x ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Co-authored-by: Ludovic Pollet <ludovic.pollet@exfo.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 3ddae77)
Thanks for #6398! |
The bugfix for this issue has been included in v1.97.5 LTS release and in v1.102.0-rc1 release. |
FYI, the bugfix has been included also into v1.93.15 LTS release. |
rtm0
pushed a commit
to rtm0/VictoriaMetrics
that referenced
this issue
Jun 8, 2024
…TEMPTY (VictoriaMetrics#6398) ### Describe Your Changes Fix for issue VictoriaMetrics#6396: according to rmdir manpage, ENOTEMPTY and EEXIST should be treated equally VictoriaMetrics#6396 ### Checklist The following checks are **mandatory**: - [x ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Co-authored-by: Ludovic Pollet <ludovic.pollet@exfo.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Running VictoriaMetrics on vXFS (vagrant filesystem) via NFS sharing consistently produces a panic error about "must-remove" files that cannot be removed, because "file exists":
On our case, this behavior seems specific to the use of vXFS filesystem (vagrant proprietary) over NFS. It cannot be reproduced with ext4 or xfs filesystems. Also tried changing various NFS option with no impact
To Reproduce
Run victoria metrics with data stored on a NFS mount backed by a vXFS filesystem
Version
victoria-metrics-20221007-005009-tags-v1.82.0-0-g832276064
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
Using strace reveals that the unlinkat syscall actually returns errno EEXISTS which is not covered by the current NFS :
We are using NFS, so the
unlink_at
failure is expected (expected NFS race...), but it is not catched by VM due to the code used here (EEXIST) vs the one searched by VM (ENOTEMPTY) in isTemporaryNFSError (dir_remover.go).The text was updated successfully, but these errors were encountered: