Dragonfire
-
Posts
8 -
Joined
-
Last visited
Posts posted by Dragonfire
-
-
7 minutes ago, sjoenh said:
Bump. -> Share a file with a user without requiring the other user to have or install Resilio Sync.
How should that work?
More important from my view is, that file shares are automatic synced to all peers of an ID
-
+1
More scenario are described here
Message Quote:
On 31.7.2017 at 9:13 PM, thobarth said:Dear Resilio team,
OK, so you implemented sharing single files. This looks useful at first glance, but in the end, it does not help us much, because it is not thought to the very end:
1.) A user sharing a file wants to close down his laptop shortly after creating the share link. So, there must always be a peer who picks up the file ASAP after creating the link. We want to configure either a share, or a set of peers, where the shared file are all sent to, and who will accept and download them all, so I can drive home while others can receive the file. My colleague wanted to send me a 80MB file today using the feature, and then go home, while I still was in a meeting. I needed the file after the meeting. For such a case, the feature is totally useless without propagating the file to an always-on peer.
2.) Simple deep links to existing files on existing shares. Requested so often. The explorer/finder plugin should offer a menu item to generate a deep link to a file or directory that already exists on a share. This is just for convenience, to embed file URLs in email, Slack, Intranets and other documents, and enable users to find them without browsing the folder structure manually.
3.) A configurable rewrite pattern (per share) to generate web URLs. We want to install a web server on one of the always-on peers, or maybe a WebDAV or SMB server or something like this. Just let us configure a pattern to rewrite the path or a file or directory in a Resilio share to a URL with a configurable pattern. As soon as the always-on peer receives the file, it will make it accessible there. Per-share configuration should be synced to any peer. Internal users could click the generated URL, and the installed web application could even allow them to manage external https share links for the files there.
Best,
Thorsten
-
On 31.7.2017 at 9:13 PM, thobarth said:
Dear Resilio team,
OK, so you implemented sharing single files. This looks useful at first glance, but in the end, it does not help us much, because it is not thought to the very end:
1.) A user sharing a file wants to close down his laptop shortly after creating the share link. So, there must always be a peer who picks up the file ASAP after creating the link. We want to configure either a share, or a set of peers, where the shared file are all sent to, and who will accept and download them all, so I can drive home while others can receive the file. My colleague wanted to send me a 80MB file today using the feature, and then go home, while I still was in a meeting. I needed the file after the meeting. For such a case, the feature is totally useless without propagating the file to an always-on peer.
2.) Simple deep links to existing files on existing shares. Requested so often. The explorer/finder plugin should offer a menu item to generate a deep link to a file or directory that already exists on a share. This is just for convenience, to embed file URLs in email, Slack, Intranets and other documents, and enable users to find them without browsing the folder structure manually.
3.) A configurable rewrite pattern (per share) to generate web URLs. We want to install a web server on one of the always-on peers, or maybe a WebDAV or SMB server or something like this. Just let us configure a pattern to rewrite the path or a file or directory in a Resilio share to a URL with a configurable pattern. As soon as the always-on peer receives the file, it will make it accessible there. Per-share configuration should be synced to any peer. Internal users could click the generated URL, and the installed web application could even allow them to manage external https share links for the files there.
Best,
Thorsten
I agree on all points, currently the file sharing feature is not used, because if you create a "File Share" you must add it to at least one "NAS" by hand.
Can you maybe add an option to push/sync "file shares" to different devices, e.g. that my NAS automatic download all "File Shares" from one ID.
Edit: Same as here
-
Finally I solved the issue ...
I mounted the hdd as `rslsync` user with
sudo mount -t ntfs-3g -o uid=rslsync,gid=rslsync,big_writes,async,noatime /dev/sda1 /media/Seagate
and deleted some files to solve the `initial recheck` errors
[20161221 13:45:18.108] JOURNAL[9C16]: Error downloading file Camera/IMG_20160317_143649931_HDR.jpg: initial recheck
Maybe is it realated to ntfs permission limitations ...
https://wiki.archlinux.org/index.php/NFS/Troubleshooting#Group.2FGID_permissions_issues
-
Seagate is an external hdd.
5 minutes ago, Helen said:And what file system is on that partition? fuseblk implies it's ntfs??
Correct, it is mounted with this options:
`sudo mount -t ntfs-3g -o uid=pi,gid=pi,big_writes,async,noatime /dev/sda1 /media/Seagate`
-
Command executed without any problems ...
I also run: `touch -mt 1411171533 /media/Seagate/Sync/DCIM/Camera/*`
Still indexing
and now I have some errors messages in the web gui:
log
[20161219 23:37:11.027] JOURNAL[9C16]: tf completed for "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" - avg hash speed: <unknown> [20161219 23:37:11.027] Update have pieces for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", was: 0, now: 84 [20161219 23:37:11.027] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[type:1 s:2732597 mt:1481933858 h:44C3AD768906EB26C3567E49288A414E4F6FA0C0] [20161219 23:37:11.027] Update have pieces for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", was: 84, now: 0 [20161219 23:37:11.027] JOURNAL[9C16]: set fs error for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", type 1, will be recreated (R/O) [20161219 23:37:11.027] JOURNAL[9C16]: will recreate entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", type 1 [20161219 23:37:11.029] JOURNAL[9C16]: skipping load torrent for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" - has fs error [20161219 23:37:11.029] SF[9C16] [3845]: connect files to peer, queue:0 dowloading:0/0 speed:0 [20161219 23:37:11.029] JOURNAL[9C16]: skipping load torrent for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" - has fs error [20161219 23:37:11.029] SF[9C16] [4731]: connect files to peer, queue:0 dowloading:0/0 speed:0 [20161219 23:37:11.029] ScheduledTask: "ConnectMorePeers" invoked: timer, reason:LoadTorrent failed [20161219 23:37:11.029] SF[9C16] [4731]: SyncStateWithPeer - waiting for previous merge to complete [20161219 23:37:11.029] SF[9C16] [3845]: SyncStateWithPeer - waiting for previous merge to complete ... [20161219 23:37:11.051] JOURNAL[9C16]: Setup entry job "FileEntryJob" for path "Camera/IMG_20160406_185446930_HDR.jpg", next state is "PERFORM", queue size 0 1 425 [20161219 23:37:11.051] JOURNAL[9C16]: file entry job for path "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:37:11.051] JOURNAL[9C16]: { "dl_failed": false, "file_hash": "44C3AD768906EB26C3567E49288A414E4F6FA0C0", "file_id": "2049:117707", "fs_error": true, "have_pieces": 0, "ignored": false, "info_hash": "9E584832152A442E1068D7FB64843B5E2FAF1430", "invalidated": false, "link_content": "", "locked": 0, "mtime": 1459961688, "name_on_disk": "IMG_20160406_185446930_HDR.jpg", "otime": 1031, "owner": "1183A21AC3AEC2CFA4DD184EE1247D901AB6F6B9", "path": "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", "perm": 420, "ph_ext": ".rsls", "placeholder": false, "pvi": "pvi[type:1 s:2732597 mt:1481933858 h:44C3AD768906EB26C3567E49288A414E4F6FA0C0]", "select_children_for_dl": false, "selected_for_dl": true, "size": 2732597, "state": 1, "time": 1459961688, "total_pieces": 84, "type": 1 } [20161219 23:37:11.053] JOURNAL[9C16]: entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" has state CREATED, current/desired entry type: 1/1 [20161219 23:37:11.053] JOURNAL[9C16]: writing new attributes to file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:37:11.053] SyncFileEntry: writing file attributes to file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", mt:1459961688 [20161219 23:37:11.054] SyncFileEntry: Failed to write attributes for file /media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg - 1 [20161219 23:37:11.054] SyncFileEntry: Can't set file attributes 0 for file /media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg - 1 [20161219 23:37:11.054] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[NULL] (reset) [20161219 23:37:11.054] Finished downloading file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:37:11.054] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[NULL] [20161219 23:37:11.054] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[NULL] (reset) [20161219 23:37:11.054] JOURNAL[9C16]: erase file_id 2049:117707 assigned to entry with path "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:37:11.054] JOURNAL[9C16]: assign file_id 2049:117707 to entry with path "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:37:11.054] [OnNotifyFileChange] "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:37:11.055] JOURNAL[9C16]: remote entry job complete for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", result = 1 [20161219 23:37:11.055] JOURNAL[9C16]: { "dl_failed": false, "file_hash": "44C3AD768906EB26C3567E49288A414E4F6FA0C0", "file_id": "2049:117707", "fs_error": false, "have_pieces": 84, "ignored": false, "info_hash": "9E584832152A442E1068D7FB64843B5E2FAF1430", "invalidated": false, "link_content": "", "locked": 0, "mtime": 1459961688, "name_on_disk": "IMG_20160406_185446930_HDR.jpg", "otime": 1031, "owner": "1183A21AC3AEC2CFA4DD184EE1247D901AB6F6B9", "path": "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", "perm": 420, "ph_ext": ".rsls", "placeholder": false, "pvi": "pvi[NULL]", "select_children_for_dl": false, "selected_for_dl": true, "size": 2732597, "state": 1, "time": 1459961688, "total_pieces": 84, "type": 1 } ... [20161219 23:37:26.600] Entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" was updated, current state: pvi[type:1 s:2732597 mt:1481933858 h:0000000000000000000000000000000000000000], expected: pvi[type:1 s:2732597 mt:1459961688 h:44C3AD768906EB26C3567E49288A414E4F6FA0C0] [20161219 23:37:26.600] FC[9C16]: fs event for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" t:1481933858 s:2732597 id:2049:117707 type:1 [20161219 23:37:26.601] Entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" was updated, current state: pvi[type:1 s:2732597 mt:1481933858 h:0000000000000000000000000000000000000000], expected: pvi[type:1 s:2732597 mt:1459961688 h:44C3AD768906EB26C3567E49288A414E4F6FA0C0]
-
I have nearly the same problem. Only my files from the Android Phone on the new Sync 2.4.4 client on my raspberry indexing all the time ...
(With 2.0.93 on a different raspberry I have no problems ...)
[20161219 23:38:33.330] JOURNAL[9C16]: tf completed for "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" - avg hash speed: <unknown> [20161219 23:38:33.330] Update have pieces for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", was: 0, now: 84 [20161219 23:38:33.330] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[type:1 s:2732597 mt:1481933858 h:44C3AD768906EB26C3567E49288A414E4F6FA0C0] [20161219 23:38:33.330] Update have pieces for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", was: 84, now: 0 [20161219 23:38:33.330] JOURNAL[9C16]: set fs error for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", type 1, will be recreated (R/O) [20161219 23:38:33.330] JOURNAL[9C16]: will recreate entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", type 1 [20161219 23:38:33.331] JOURNAL[9C16]: Setup entry job "FileEntryJob" for path "Camera/IMG_20160406_185446930_HDR.jpg", next state is "PERFORM", queue size 0 1 427 [20161219 23:38:33.331] JOURNAL[9C16]: file entry job for path "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:38:33.331] JOURNAL[9C16]: { "dl_failed": false, "file_hash": "44C3AD768906EB26C3567E49288A414E4F6FA0C0", "file_id": "2049:117707", "fs_error": true, "have_pieces": 0, "ignored": false, "info_hash": "9E584832152A442E1068D7FB64843B5E2FAF1430", "invalidated": false, "link_content": "", "locked": 0, "mtime": 1459961688, "name_on_disk": "IMG_20160406_185446930_HDR.jpg", "otime": 1031, "owner": "1183A21AC3AEC2CFA4DD184EE1247D901AB6F6B9", "path": "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", "perm": 420, "ph_ext": ".rsls", "placeholder": false, "pvi": "pvi[type:1 s:2732597 mt:1481933858 h:44C3AD768906EB26C3567E49288A414E4F6FA0C0]", "select_children_for_dl": false, "selected_for_dl": true, "size": 2732597, "state": 1, "time": 1459961688, "total_pieces": 84, "type": 1 } [20161219 23:38:33.333] JOURNAL[9C16]: entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" has state CREATED, current/desired entry type: 1/1 [20161219 23:38:33.333] JOURNAL[9C16]: writing new attributes to file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:38:33.333] SyncFileEntry: writing file attributes to file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", mt:1459961688 [20161219 23:38:33.333] SyncFileEntry: Failed to write attributes for file /media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg - 1 [20161219 23:38:33.333] SyncFileEntry: Can't set file attributes 0 for file /media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg - 1 [20161219 23:38:33.333] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[NULL] (reset) [20161219 23:38:33.333] Finished downloading file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:38:33.333] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[NULL] [20161219 23:38:33.333] Set new pvinfo for file "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" = pvi[NULL] (reset) [20161219 23:38:33.333] JOURNAL[9C16]: erase file_id 2049:117707 assigned to entry with path "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:38:33.333] JOURNAL[9C16]: assign file_id 2049:117707 to entry with path "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:38:33.333] [OnNotifyFileChange] "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg" [20161219 23:38:33.334] JOURNAL[9C16]: remote entry job complete for entry "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", result = 1 [20161219 23:38:33.334] JOURNAL[9C16]: { "dl_failed": false, "file_hash": "44C3AD768906EB26C3567E49288A414E4F6FA0C0", "file_id": "2049:117707", "fs_error": false, "have_pieces": 84, "ignored": false, "info_hash": "9E584832152A442E1068D7FB64843B5E2FAF1430", "invalidated": false, "link_content": "", "locked": 0, "mtime": 1459961688, "name_on_disk": "IMG_20160406_185446930_HDR.jpg", "otime": 1031, "owner": "1183A21AC3AEC2CFA4DD184EE1247D901AB6F6B9", "path": "/media/Seagate/Sync/DCIM/Camera/IMG_20160406_185446930_HDR.jpg", "perm": 420, "ph_ext": ".rsls", "placeholder": false, "pvi": "pvi[NULL]", "select_children_for_dl": false, "selected_for_dl": true, "size": 2732597, "state": 1, "time": 1459961688, "total_pieces": 84, "type": 1 }
mount
Quote/dev/sda1 on /media/Seagate type fuseblk (rw,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
I was able to`chmod` all files and also to change the mtime with`touch` command as pi user.
How can I give the user `rslsync` correct permissions?
[Now Implemented!] Share A Single File
in Feature Requests
Posted
Your first implementation has a lot of problems, because typically you sit behind a NAT, Firewall and other stuff