[read-only-folder not updating completely, torrent errors]

thanks nils. i diffed the contents of both folders, and the read-only does contain everything (except syncignored files) plus undeleted folders.

 

so theres nothing missing, the numbers in the UI are wrong. and folders do not get deleted. i wrote an email regarding both to the team.

[read-only-folder not updating completely, torrent errors]

hi,

 

on my desktop btsync says "1.3GB in 1067 files". on a second machine with read-only-access it says "1.0 GB in 1023 files". Additionally, files i delete on the Desktop are not deleted in the read-only folder.

 

I create those folder by initially copying it with external hard drives between my machines, as the network is quite slow. i already tried removing and re-adding the folder to btsync on both machines.

 

Logs are not helpful here, although recently i get some of these:

 

[date] Download using patch (diff:0) path/to/file/IMGP1903.JPG
[date] [OnNotifyFileChange] /mnt/usbhdd/path/to/file/IMGP1903.JPG
[date] Finished downloading file path/to/file/IMGP1903.JPG, writing file attributes mt:1281548390
[date] [OnNotifyFileChange] /mnt/usbhdd/path/to/file/IMGP1903.JPG
[date] Torrent magnet (<some hash>) status:137 error:<NULL> meta:0 conns:1 io:0
[date] Torrent IMGP1903.JPG status:137 error:<NULL> meta:1 conns:0 io:0
[date] Force unloading torrent IMGP1903.JPG
 

although i can't find any that seem connected to the incomplete folder.

 

btsync versions are newest.

 

any ideas?

[sync.log growing into gigabytes]

hi,

i have btsync running on an raspberry pi and the sync.log grew until there was no space left on the sd card, by then it reached 12GB.

is this a bug or the usual behaviour for logfiles and i need to logrotate?

thanks,

jaykay

[Syncing questions]

today i learned you need to search for "nested" sync folders to find some discussions about 3.

tl;dr: not possible with btsync right now, but support probably gets added at some time or another.

under windows moving the nested folder somewhere else and creating a link inside the old folder should work fine, as long as you don't need paths like \parentDirectory\link\someSubdirectory to work. othwise you could create symlinks, but i do not know how btsync handles these.

[synced folder inside synced folder]

@greatMarko: i thought about how to search for this, but "nested" didn't cross my mind, thanks.

@joebush: don't ask why i didn't try it out with some test dir...

@Shot2: thats what i thought, i didn't see any reason why it shouldn't work.

thanks guys!

[synced folder inside synced folder]

why shouldnt it be possible?

generate secrets for /data/readdir/, and start syncing with the read-only secret.

then generate secrets for /data/readdir/writedir/, and add this folder on all machines with the full access secret.

expected behaviour:

peer writes to readdir: nothing happens.

peer writes to readdir/writedir: the change gets synced.

main machine writes anywhere: the change gets synced.

can bittorrent sync handle this?

edit: does it change anything if i said /data/readdir/ from my main machine gets synced to other devices as usual, but /data/readdir/writedir gets synced to another location on those other devices, not into a subfolder of the original sync dir?

[Listening Port: what for & how to set?]

as i said, for me it *just works*, without dyndns or any port settings.

and everyone who has the secrets has access, noone else.

[Listening Port: what for & how to set?]

in my case, i have an RPi behind a router with a dynamic ip.

and it just works, even without setting a listening port and port forwarding. i don't know why, but hey, it works. i guess this is the magic of the bittorrent-protocol

when you need other services to access your RPi from outside you LAN, google "dyndns".

[synced folder inside synced folder]

i have a large folder, which is backupped by two devices with read access.

one subfolder should be synced with the same machines with read/write access, as i want to use it like a dropbox.

how to set this up is clear, but my question is whether bittorrent sync will handle this correctly, as in not trying to write a new file two times, as it is in two sync folders

regards,

jaykay