Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finish voyager payments #94

Closed
2 tasks
Tracked by #90 ...
juliangruber opened this issue Apr 11, 2024 · 10 comments
Closed
2 tasks
Tracked by #90 ...

Finish voyager payments #94

juliangruber opened this issue Apr 11, 2024 · 10 comments
Assignees

Comments

@juliangruber
Copy link
Member

juliangruber commented Apr 11, 2024

@juliangruber juliangruber mentioned this issue Apr 11, 2024
Closed
@juliangruber juliangruber self-assigned this Apr 11, 2024
@juliangruber juliangruber mentioned this issue May 22, 2024
16 tasks
@juliangruber

This comment was marked as duplicate.

@juliangruber
Copy link
Member Author

Still exporting Voyager measurements, currently at 3.7TB

@juliangruber juliangruber mentioned this issue Jul 24, 2024
25 tasks
@juliangruber
Copy link
Member Author

Still exporting Voyager measurements, currently at 16TB

@juliangruber
Copy link
Member Author

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.

@juliangruber
Copy link
Member Author

juliangruber commented Jul 30, 2024

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.

@patrickwoodhead patrickwoodhead mentioned this issue Jul 31, 2024
36 tasks
@juliangruber
Copy link
Member Author

juliangruber commented Aug 12, 2024

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.

@juliangruber
Copy link
Member Author

juliangruber commented Aug 23, 2024

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 :|

@juliangruber
Copy link
Member Author

Worst case we will resume from the cursor 2 weeks ago, and delete the last export

@juliangruber
Copy link
Member Author

Finish this issue by iterating over the participants table

@patrickwoodhead patrickwoodhead mentioned this issue Sep 3, 2024
22 tasks
@juliangruber
Copy link
Member Author

juliangruber commented Sep 17, 2024

1359.54 FIL have been paid to 4333 participants 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants