Note: Frequency is subject to change. Although it's been quite a while without issue so it's probably fine here.
Frequency: 145.785 (Simplex)
C4FM ID: 00 (required for C4FM/Wires-X)
Location: Sterling, Va, USA
Grid Square: FM19ha
Station Call: KG4TIH
WIRES-X Node: KG4TIH-ND3 (71429)
Default Room: VA-Sterling (28558)
Transmit Power: 40w
Coordination: N/A
After a bit of moving hardware around my 449.375 Wires-X repeater is back online.
Frequency: 449.375-
Tone: 110.9hz (required for analog)
C4FM ID: 00 (required for C4FM/Wires-X)
Location: Sterling, Va, USA
Grid Square: FM19ha
Station Call: KG4TIH
WIRES-X Node: KG4TIH-ND (18558)
Default Room: VIRGINIA (21625)
Transmit Power: 50w
Coordination: TMARC
This document which covers what we know of the NDS-4600 has been written with help from /u/Offspring.
Thanks to a note and a good find by /u/DerUlmer I can now say there is a known way to change the zoning for the NDS-4600:
See the section for "Changing the zoning"
https://blog.carlesmateo.com/2019/06/07/dealing-with-performance-degradation-on-zfs-draid-rebuilds-when-migrating-from-a-single-processor-to-a-multiprocessor-platform/
Note: I've not tested this (yet).
The real problem with cloud computing isn't what you'd think: It's the inability to use important troubleshooting tools like percussive maintenance.
Need to run a reweight by utilization but can't with octopus? Try this...
ceph osd reweight-by-utilization 0.5 -- 150
Errors:
Up until now I've been cooling the thermally (and physically) isolated server room from the rest of my house and using a large mini-split to keep it cool. However the mini-split has reached its limits; The room now has 9-10 kW of gear in it.
Installing Bacula on CentOS 7 using the Community RPMs (from Bacula.org) for 9.6.7 and other versions is a bit annoying to get Postgres...
yum install bacula-postgresql --exclude=bacula-mysql --exclude=mariadb
Errors you might get otherwise...
A few of my Ceph nodes with 60-ish disks each were experiencing frequent reboots. Turns out kernel.nmi_watchdog was rebooting it due to disks holding it up under very high load. By turning it off via `echo "kernel.nmi_watchdog=0" > /etc/sysctl.d/99-watchdog.conf` the problem was solved. Although I suspect there are better ways to tune NMI Watchdog to fix this. I'm being lazy.
Hosts in my cluster all have two 10GbE links to a switch bonded with LACP. That gives them an effective link of 20GbE normally. But really, even 5Gbps would be enough for most hosts. The kernel in most boxes combined with drivers and such isn't going to be able to push 20GbE, much less 40GbE. So faster isn't worth it.
Note: Don't bother with IPoIB. You're better off with 10GbE x2 via LACP. Although if it's a choice between 40Gbps IB and IPoIB or a couple of 1GbE lines, go IPoIB.