mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #45] incron / lsyncd (inotify or fsevents) not detecting changes at s3. #25
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#25
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 @paulm17 on GitHub (Jun 28, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/45
Hi,
I've been pulling my hair out all day on finding out why an s3fs mounted directory won't be updated via incron or lsyncd.
Then I happened to come across this:
I am running the latest fuse:
I created the rpms myself for centos 6.5.
and the latest s3fs:
Yet, when the s3 bucket is updated, the change is available when i view the s3fs mount point but incron or lsyncd do not update nor to they do suggest any activity in their logs.
However, if I go into the s3fs mount and I do an update there. Everything works as it should.
So why am I having the issue of nothing being detected when a change at s3 happens?
Thanks
@thenickdude commented on GitHub (Jun 29, 2014):
S3 can't notify your instance when files change in the bucket (the only
notification it supports is a lost-file notification), so I don't see how
such a feature could be implemented for s3fs.
@paulm17 commented on GitHub (Jun 29, 2014):
Taking s3 out of this for a moment.
If I swap out s3 and use nfs and use lsyncd to monitor the files. This works fine.
So the question is, under s3fs. When a new file suddenly appears or a change is made. Why can't s3fs be made aware on the file system level?
@muvimotv commented on GitHub (Aug 19, 2014):
where did you get these from:
fuse-devel-2.9.3-1.el6.x86_64
fuse-libs-2.9.3-1.el6.x86_64
fuse-2.9.3-1.el6.x86_64
@muvimotv commented on GitHub (Aug 19, 2014):
i can't manage to get s3fs to work at all on 6.5
@muvimotv commented on GitHub (Aug 19, 2014):
i follow the instruction to make and then i get this:
modprobe fuse
FATAL: Module fuse not found.
@paulm17 commented on GitHub (Aug 19, 2014):
Hi,
I abandoned this in the end. Just so you know, I made my own libs from source rpms.
Thanks
Paul
@muvimotv commented on GitHub (Aug 19, 2014):
ok well i guess i can forget all together about using s3fs i've spend 2 days on this already and i'm not any closer to have it working as i was when i started... There is no tutorial anywhere that actually work and since i basically have no clue what i'm doing i don't see how i can sort this out on my own...
@ggtakec commented on GitHub (Sep 7, 2014):
I think inotify do not work on s3fs, because s3fs run on fuse. It likes NFS.
(I think that maybe some system(ex. nfs/nfs_kq) can do it, but it is polling file stats.)
Thus s3fs runs on fuse, so inotify is hard to support. If s3fs supported, but it could not be good performance and not be respond as soon as changing.
So no1youknowz had used another tool which supports notify, I want to know it, and see codes.
It helps us to support notify, if it can do, I try to add s3fs.
Thanks,
@micgrivas commented on GitHub (Feb 12, 2019):
inotify cannot work on s3fs, because s3fs works over HTTPS. Practically, it is the same as DAV.
The s3fs makes a pseudo-filesystem, for our ease, but cannot be 100% a file system.
Each time one copies files to s3 (over a mount with s3fs) , then the s3fs creates a local file and then run an HTTP request to upload it.
There is no way for such a system to understand changes in s3-subsystem. Like an apache server will not automatically find any changes in the /var/lib/www directory and refresh any page.