• Content Count

  • Joined

  • Last visited

About sync-ohoy

  • Rank
    New User
  1. Thank you but your suggestions does not help much. If I could move the whole share I would. I want to keep the main project share in it's current location, it is only one project that has grown too much that I right now need to move elsewhere. Now, how does btsync handle mountpoints? And symlink is usually a quite excellent tool, it's only this particular setup with btsync that is an issue.
  2. Having a share with subfolders synced between several machines. Now one machine is full so I need to move one of the subfolders onto an external disk. I don't want any changes in the share for any of the other machines. I moved the subfolder to the external disk and symlinked back into the share. Big mistake, btsync doesn't follow symlinks so the subfolder was removed from all other machines and replaced by a (then broken) link... I've spend several hours already restoring the share from .sync and it's still a mess with all timestamps set to just now and lots of older files that already was in .sync when this huge deletion found it's way there... If I instead of symlink back to the share "mount --bind" the folder on external disk into the share will this be treated as a local folder by btsync? Not messing up the share again? I neither have time nor will to experiment risking a messup again. All machines is various linux.
  3. From work machine I've rerendered the files into the folders they were deleted from. 2 folders with 375 images each. I cleaned up storage on the misbehaving laptop and restarted btsync on it. It synced all files more recent than the folders it messed with before but those two it continue f***ng up, deleting about half rerendered files in them. It deletes the files from my other shares and they are NOT moved to .sync. Only about half the files from each folder shows up in archive on both on work stationary and server. (and it's not the other half missing from the folders, it's random files from the sequences, both deleted and still present ones). Hopefully I haven't lost anything else, more critical, than these two render folders.
  4. I think this behaviour is very dangerous and can cause much damage and dataloss! Wouldn't it be wise to have som kind of protections so clients doesn't doesn't start to delete files from other machines when they are full? I forgot that the laptop was on and syncing when I started a new job using a lot of space (About 100Gb so far so reducing a log from 100Mb wouldn't do much...)
  5. I noticed today at work that files I was adding to sync, rendered animation image files so quite a lot and quite large, was dissapearing from their folders. It looked like it was a laptop with not too much storage that was deleting the files. Sure enough, the laptop was filled to the brim, not a single Kb left. It had started to send deletions and replacement files of 0Kb size to my other machines... I pulled the plug on that one and don't want to turn it on before I find out what damage it did so I don't know what version of BTsync it ran, but it was older than the 1.4.103 I have on my work machine and on my server. How can machines be allowed to do this when they are unable to download the synced files themselves? It's quite serious I think.
  6. I installed BTsync at my Debian server (arm) but it keeps segfaulting after running a little while. After restarting BTsync the folder list in the webui is empty so I have readded the shares a few times (3 other machines were already synced so I added with existing secret keys). Suddenly the size column reported 0b in 0 files for one of the shares. Checking shares on another machine it rapidly decreased in size, deleting files. I quickly killed btsync on the debian server but about half of the files had evaporated from all synced machines. Luckily I had one machine that was turned off during all this so I managed to rescue my files from that one by booting it without network connection, making backups of the shares and plugging it to the network agian. The shared files on that machine then also suddenly we're removed... I then copied the files back from the backups and now all machines connected to the shares are back with all files. Except the debian server of course. I don't dare to connect that one again... No why did it start with this behaviour, deleting files? And how can I prevent this from happening again? Right now BTsync doesn't feel safe to use for me.