Is this the smallest syncthing device?

It’s a Raspberry Pi Zero W. The usb cable is for power.

sda           8:0    1 116.9G  0 disk
└─sda1        8:1    1 116.9G  0 part /mnt/stik1
mmcblk0     179:0    0  59.5G  0 disk
├─mmcblk0p4 179:4    0  52.5G  0 part /mnt/data
├─mmcblk0p2 179:2    0   3.9G  0 part /
├─mmcblk0p3 179:3    0   2.9G  0 part [SWAP]
└─mmcblk0p1 179:1    0   250M  0 part /boot`

Does it work? :slight_smile:

Yes, of course!:slight_smile:

1 Like
top - 15:05:33 up  2:44,  1 user,  load average: 0.19, 0.12, 0.10
Tasks:  99 total,   1 running,  98 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1.7 us,  1.3 sy,  0.0 ni, 97.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:    493260 total,   365192 used,   128068 free,    58644 buffers
KiB Swap:  3018748 total,        0 used,  3018748 free.   168416 cached Mem

 1372 root      20   0    5100   2372   2016 R  1.6  0.5   0:04.39 top
  453 david     23   3  801516  38556  10424 S  0.3  7.8   3:22.69 syncthing
  861 root      20   0   12236   5308   4600 S  0.3  1.1   0:00.79 sshd
    1 root      20   0    5404   3936   2780 S  0.0  0.8   0:04.68 systemd
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.01 kthreadd
    3 root      20   0       0      0      0 S  0.0  0.0   0:02.42 ksoftirqd/0
    5 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 kworker/0:0H
    7 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 lru-add-drain
    8 root      20   0       0      0      0 S  0.0  0.0   0:00.01 kdevtmpfs

I’m trying to build a fleet of these. Takes a really long time to scan and syncing is sloooooow (12,000 items with 65GB, so kinda expected). But they seems to work. My whole cluster got out of whack and I had to wipe and start over (all indication is that it was self-inflicted)

These are the textbook use-case of needing “receive only” folders. They have no users typically. I am using them as tiny web servers (content needs to be pushed out, but is not generated on device)

1 Like

I’m using this since few months and it works as well :slight_smile: Only difference I’ve attached an external HD but I had to use a “Y” cable to power it externally with the same power source used for the board… unfortunately those tiny boards have limited current on their usb ports.

(almost same scope, receive only device to backup a remote folder)

1 Like

Yeah, I’ve found the most reliable way is to use 128GB MicroSD cards. USB flash drives can work too, but many of them are not engineered for 24/7 operation and overheat.

I’d posit that this one is the smallest Syncthing device (at least per/GB, it has 128GB onboard)

1 Like

As I have 64GB on sd and 128GB on usb, I have 50% more storage. The usb drive is less than 50% the volume of the encased pi, so you aren’t beating me on your measure.:slight_smile:

[edit] Mind you, if you stuck in a 128GB flash drive…:stuck_out_tongue_winking_eye:

[edit] Mind you, if you stuck in a 128GB flash drive…:stuck_out_tongue_winking_eye:

OK, how about 2x128GB :wink: we can call it a tie if you like, since I have four of those flash drives, and the Pi0 in the back has four USB ports, though I’m not sure it can power that many.

(also, smallest syncthing cluster, all three of those are syncing the same data)


Cool to see syncthing working on such a tiny device!

But I think us VM syncthing users have you beat! What’s smaller than virtual? =)

I’m happy to announce that my virtual instances of syncthing have been running without issue for over 340 days. This is an amazing project.

1 Like

Nice try!:slight_smile: A VM isn’t a device.:stuck_out_tongue:

Ha! You are right! I just wanted to take a poke at the tiny device syncthing users.

I do have a question. Will it do reasonable one way syncs with large file systems after initial sync? For example 2+ TB?

It’s not so much the amount of data, more how much it changes.

As you can see from my 3rd post, when not doing very much, it uses less than 1% cpu. This a lot better than a couple of years ago. It’s been tweaked over time to make it more efficient.

If syncthing has real work to do, it maxes out the cpu, especially when hashing and at startup.

So, providing you start with pre-copied data and don’t change 20% of it daily, then it’s worth a go.

It doesn’t cost a fortune.

1 Like

My cluster is syncing two folders. On with 12 thousand small files at 8,7GB and one with 750 files at 65GB.

Given it’s performance I would not expect 2+ TB to work well, but should work. Initial Sync takes about 48 hours, Thereafter, it seems to keep up fine. I’ve tested adding and subtracting a couple GBs with no issues.

1 Like

Pre-copied data got me into a world of hurt with sync conflicts (I really need a receive only option). Since I rebuilt the cluster with all data populated by syncing, it has been working fine

It worked for me.

Thank you both for your input. You are correct, its not how much data is synced . . . It’s how much the synced data changes.

I have almost 2TB in a one way sync, and I can validate that the scan process takes a good amount of time and uses a reasonable amount of CPU during the scan. The initial sync is brutal for large volumes of data, but I am confident that is entirely up to the network connection one is using to perform that first sync.

The Zsun card reader running LEDE is able to run syncthing and transfers at around 64KiB/sec. I have it running with a 64GB micro SD card and it uses 0.72W when idle (wifi connected) and around 1W when doing data transfer over wifi.

It can do around 3.5-4MB/sec writes over smb share

It looks larger in the photos than it really is. I doubt there is much smaller!

The orange pi/nanopi boards are probably a better size/performance ratio. This would have been ideal if it didn’t have such flaky wifi drivers:

Another tip for squeezing storage out of SBCs - use this sd card reader, it has the GL3224 which allows you to access both slots simultaneously

1 Like