mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #779] I/O errors when running iozone on s3fs mounted file system #450
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#450
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @apjvanloo on GitHub (Jun 21, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/779
Additional Information
I am running iozone with the following command line on an s3fs mounted file system:
iozone -R -I -u 3 -r 1m -s 256m -F /mnt/s3fs/s3fs-test-bucket-dv/test/1 /mnt/s3fs/s3fs-test-bucket-dv/test/2 /mnt/s3fs/s3fs-test-bucket-dv/test/3
During the iozone test with 2 concurrent processes the following error occurs:
Error in file: Found ?0? Expecting ?f4f4f4f4f4f4f4f4? addr 7f384c800000
Error in file: Position 267386880
Record # 255 Record size 1024 kb
where 0x7f384c800000x loop 0
In the next test stage I then receive the following error and iozone hangs:
/mnt/s3fs/s3fs-test-bucket-dv/test/1: No such file or directory
Version of s3fs being used (s3fs --version)
V1.83(commit:3bf05da) with OpenSSL
Version of fuse being used (pkg-config --modversion fuse)
2.9.2
System information (uname -r)
3.10.0-862.3.2.el7.x86_64
Distro (cat /etc/issue)
CentOS Linux release 7.5.1804 (Core)
s3fs command line used (if applicable)
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
Details about issue
iozone output:
@gaul commented on GitHub (Jan 24, 2019):
Could you test again against master? #918 addresses symptoms similar to this issue.
@gaul commented on GitHub (Apr 9, 2019):
Closing due to inactivity. Please reopen if symptoms persist.