GooseBerry

I've updated /etc/defaults/cpufrequtils accordingly: # WARNING: this file will be replaced on board support package (linux-root-...)$ ENABLE=true MIN_SPEED=408000 MAX_SPEED=1512000 GOVERNOR=ondemand But no change. Still the CPU only goes up to 1296000Hz. Update: now it works..! I had to restart the service: sudo systemctl restart cpufrequtils

I have a similar issue. My Rock64 doesn't seem to higher than 1296000Hz when 100% stressed using "stress -c 8 -t 60s &". roy@rock64:~$ stress -c 8 -t 60s & [1] 23003 stress: info: [23003] dispatching hogs: 8 cpu, 0 io, 0 vm, 0 hdd roy@rock64:~$ cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq 1512000 roy@rock64:~$ cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq 408000 roy@rock64:~$ cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq 1296000 stress: info: [23003] successful run completed in 60s [1]+ Done stress -c 8 -t 60s

I have been playing with Docker and Samba for a while now, and I'm not confident that this is the way to go. Samba is quite picky with regard to network configurations as it relies on broadcast messages. As Docker containers, and especially swarm services, have a dedicated internal network, the set-up becomes complicated and rigid. This looses many of the Docker benefits. Thus, I'm back to my original idea of the Samba+CTDB combo. Mixed with Ceph, this may be an interesting little project, but first I'll need to get me some hardware... I also found an article on this subject here.

Looking at the various pointers and links provided, I'm now convinced that GlusterFS is not the way to go and the Docker Swarm mode looks really appealing. Thus for the distributed storage, probably Ceph RBD would be a good starting point, as it is provided as a standard volume driver for Docker. As all these are new grounds for me, I have no clear picture on how to configure networking, dns and dhcp such all works reliably regardless which node is operational. I'll will first give Docker and Ceph a try on my two BPi and see what I bump in to....

Thanks Stuart for your elaborate response. I have no experience with containerised/virtualize servers, but in the case I would go for an N+1 clustered NAS, what form would be preferable for Samba? Are there easy to deploy/maintain solutions (free, open source) already out there?

With regard to Rock64 as a NAS... As I had my share of struggles with RAID, I'm walking around with the idea to get started on the following project: Instead of having a server with multiple disks, why not have multiple servers in fail-over configuration. With a cheap-ass Rock64, this will not cost much more... Hardware, 2 identical sets consisting of the following: Rock64 with its 5V/3A PSU, USB3.0 storage (SSD or HDD), mSDcard for the root file system Software, on each: Armbian, Samba, CTDB, DNS, DHCP, all in failover configuration with common GlusterFS shared storage. Additionally, OpenVPN on each (no fail-over, just on 2 different WAN ports) to have remote access to my home network. IMO, this should have the potential to work and achieve a reasonable performance, and with rclone to AWS S3 you would be disaster-proof as well... What do you think, can it fly, should I re-consider, or should I bail-out ...