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: can't remove 'test': I/O error #2395
Comments
I find |
@FlowerBirds If you are able, try the following:
Thanks in advance for your assistance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Additional Information
Version of s3fs being used (
s3fs --version
)s3fs 1.19
Version of fuse being used (
pkg-config --modversion fuse
,rpm -qi fuse
ordpkg -s fuse
)LAPTOP-TC4A0SCV:/data/test4/s3fs-fuse-1.93# apk list | grep fuse- fuse-exfat-1.3.0-r2 x86_64 {fuse-exfat} (GPL-2.0-or-later) fuse-openrc-3.11.0-r0 x86_64 {fuse3} (GPL-2.0-only LGPL-2.1-only) [installed] fuse-2.9.9-r1 x86_64 {fuse} (GPL-2.0-only LGPL-2.1-only) [installed] ceph-fuse-16.2.10-r1 x86_64 {ceph} (LGPL-2.1-only AND LGPL-2.0-or-later AND GPL-2.0-only AND GPL-3.0-only AND CC-BY-SA-1.0 AND BSL-1.0 AND GPL-2.0-or-later WITH Autoconf-exception-2.0 AND BSD-3-Clause AND MIT AND custom) fuse-overlayfs-1.8.2-r0 x86_64 {fuse-overlayfs} (GPL-3.0-or-later) fuse-static-2.9.9-r1 x86_64 {fuse} (GPL-2.0-only LGPL-2.1-only) fuse-overlayfs-doc-1.8.2-r0 x86_64 {fuse-overlayfs} (GPL-3.0-or-later) kio-fuse-5.0.1-r2 x86_64 {kio-fuse} (GPL-3.0-only) unionfs-fuse-doc-2.1-r0 x86_64 {unionfs-fuse} (BSD-3-Clause) fuse-doc-2.9.9-r1 x86_64 {fuse} (GPL-2.0-only LGPL-2.1-only) fuse-common-3.11.0-r0 x86_64 {fuse3} (GPL-2.0-only LGPL-2.1-only) [installed] fuse-exfat-doc-1.3.0-r2 x86_64 {fuse-exfat} (GPL-2.0-or-later) fuse-dev-2.9.9-r1 x86_64 {fuse} (GPL-2.0-only LGPL-2.1-only) [installed] rbd-fuse-16.2.10-r1 x86_64 {ceph} (LGPL-2.1-only AND LGPL-2.0-or-later AND GPL-2.0-only AND GPL-3.0-only AND CC-BY-SA-1.0 AND BSL-1.0 AND GPL-2.0-or-later WITH Autoconf-exception-2.0 AND BSD-3-Clause AND MIT AND custom) fuse-exfat-utils-1.3.0-r2 x86_64 {fuse-exfat} (GPL-2.0-or-later) py3-confuse-1.7.0-r0 x86_64 {py3-confuse} (MIT) unionfs-fuse-2.1-r0 x86_64 {unionfs-fuse} (BSD-3-Clause) confuse-dev-3.3-r0 x86_64 {confuse} (ISC) gvfs-fuse-1.50.1-r0 x86_64 {gvfs} (LGPL-2.0-or-later) confuse-doc-3.3-r0 x86_64 {confuse} (ISC) confuse-3.3-r0 x86_64 {confuse} (ISC)
Kernel information (
uname -r
)5.15.133.1-microsoft-standard-WSL2
GNU/Linux Distribution, if applicable (
cat /etc/os-release
)How to run s3fs, if applicable
[x] command line
[] /etc/fstab
s3fs syslog messages (
grep s3fs /var/log/syslog
,journalctl | grep s3fs
, ors3fs outputs
)Details about issue
Step1 unzip file
Step2 remove s3fs-fuse-1.93 folder
By observing the Wireshark packet capture, it was found that during the decompression process, the test folder was first created by calling PUT /data/test4/s3fs-fuse-1.93/test/, and then the files under the /data/test4/s3fs-fuse-1.93/test/ folder were created by calling PUT. After the files under the test folder were uploaded, PUT /data/test4/s3fs-fuse-1.93/test/ and PUT /data/test4/s3fs-fuse-1.93/ were called once again and successfully created. When manually creating a folder using mkdir test, only one PUT method was called, so the manually created folder can be deleted. However, when deleting the folder after decompression, it cannot be deleted, resulting in an I/O error.
Question:Why is it called twice to create a folder during decompression?
The text was updated successfully, but these errors were encountered: