Closed juliangruber closed 1 week ago
Now that we have all Voyager measurements in W3C, we can write a script to download them, evaluate and reward.
Still exporting Voyager measurements, currently at 3.7TB
Still exporting Voyager measurements, currently at 16TB
After 17TB, the export crashed with EFBIG
. I will remove one disk from the RAID array and resume writing measurements to it.
The process should be resumed from cursor value bafybeiayhmo4rttwwbstzdbmrf47rcmoxmuk7z2ms6wi7omg5ccjghtlda
. There will be some duplicate measurements between the end of the current export and the beginning of the new one.
I have removed /dev/sdc3
from the raid array, reformatted and mounted it:
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 32G 0 32G 0% /dev
tmpfs 6.3G 796K 6.3G 1% /run
/dev/md2 20T 17T 2.8T 86% /
tmpfs 32G 0 32G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/md1 989M 66M 873M 7% /boot
tmpfs 6.3G 0 6.3G 0% /run/user/0
/dev/sdc3 20T 3.6G 19T 1% /root/download-measurements/export/2
The old export is in export/1/voyager.txt
, the resumed export is being written to export/2/voyager.txt
.
It crashed again after writing another 17TB. The total export size at the moment is 34TB.
The process should be resumed from cursor value bafybeifwycojnl2ffj64o4lv55hwfwitoq5oln4kxxnprdwsb6jwdftode
. There will be some duplicate measurements between the end of the current export and the beginning of the new one.
The hetzner server became unreachable. I fear this means I will have to reboot it, at which point the tmux session with the output of the last cursor value will have been lost :|
Worst case we will resume from the cursor 2 weeks ago, and delete the last export
Finish this issue by iterating over the participants table
1359.54 FIL have been paid to 4333 participants 🥳