mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #1291] Checking consistency of cache file and its stat #693
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#693
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 @ggtakec on GitHub (May 18, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1291
Additional Information
Version of s3fs being used (s3fs --version)
v1.86
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
n/a
Kernel information (uname -r)
n/a
GNU/Linux Distribution, if applicable (cat /etc/os-release)
n/a
s3fs command line used, if applicable
Set multireq_max to 2 or more
/etc/fstab entry, if applicable
n/a
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
n/a
Details about issue
This is an issue derived from #1285
Start s3fs with multireq_max set to 2 or more.
When a large object (file) is read (downloaded), the consistency between the cache file and the stat information of the cache file may not match.
We would like to prepare tools so that we can investigate the possibility and cause of this inconsistency.
@gaul commented on GitHub (Jun 4, 2020):
@ggtakec does this issue need further work?
@ggtakec commented on GitHub (Jun 6, 2020):
@gaul I'm trying to add debug-only code to this issue.
Checking cache files from outside s3fs cannot be exact, so I'm trying to prepare an option and write code that can only work when the option is enabled.
So please wait a while and I'll ask you to review them.
@gaul commented on GitHub (Oct 10, 2020):
@ggtakec Is this resolved?
@qianyi-sourse commented on GitHub (Aug 17, 2023):
@ggtakec Is this resolved? I met the similar problem. After I cp a large file to the mount dir , the cache file size and source file size did not match.
@ggtakec commented on GitHub (Aug 17, 2023):
The issue is likely due to forgetting to close(because of waiting for a bug report after merging the related PR).
A lot of code has changed since when this problem occurred, so it is unknown if it still occurs.
I think there have been reports of similar events, but I think they are always checked.
(In addition, since the cache file is a sparse file, it is necessary to compare it with the cache information file contents.)
Since this issue has changed a lot of code since I made, I think we should close this issue for now.
@qianyi-sourse
Could you please post the phenomenon you are currently detecting as a new issue?
If you write #1291 as the related issue in your issue, it will be easier to track down the issue.
At that time, it would be helpful if you could write detailed information together.
In addition, since the file size may be different, please let me know the options you are using and the free disk space.
Thanks in advance for your assistance.