Unexpected unavailability for Disaster Recovery

[illwieckz]

I'm currently unavailable because of me being in disaster recovery.

Two drives started failing out of a raid array. This is a very large array and reconstructing the array will take days if not a complete week. If raid reconstruction fails, backup restoration will take days if not a complete week. This doesn't affect the Unvanquished infrastructure but this affects my ability to contribute to Unvanquished.

Code: Select all

[2805305.796048] BTRFS error (device dm-7): bdev /dev/dm-6 errs: wr 25891047, rd 27145774, flush 62680, corrupt 0, gen 0
[2805305.796082] BTRFS error (device dm-7): bdev /dev/dm-6 errs: wr 25891048, rd 27145774, flush 62680, corrupt 0, gen 0
[2805308.538539] BTRFS warning (device dm-7): lost page write due to IO error on /dev/dm-6 (-5)
[2805308.560244] BTRFS error (device dm-7): error writing primary super block to device 4

[illwieckz]

This message just to say I haven't fully recovered my working environment yet. I only had one spare disk in stock and it took more than 10 days to source the second drive because of the current scarcity. I should recover operationality around Sunday or Monday, but I will still likely avoid some Unvanquished work as redundancy will only be fully recovered after one more week. Unvanquished is just a hobby and I will not risk more important things for it.

Using my rescue laptop I worked on some things:

• The second blog post for the 0.56 release focusing on assets update and media creation pipeline work is almost ready.
• I worked on the NetRadiant map editor. The editor received a wave of new contributions and I did review and merging work for it plus some polishing.

The indiedb release post and the linuxfr.org release post aren't started yet.

[illwieckz]

Replacement of first drive is almost over:

Code: Select all

99.0% done, 0 write errs, 0 uncorr. read errs

Once this is done I'll have to replace the second drive.
The first drive was needed to secure the data, the second drive is required to secure redundancy.
So I may start using my working environment the right way starting with tomorrow, but I will still be cautious with what I do and weight any action for the coming days.

I published the second 0.56 blog post anyway:

• https://unvanquished.net/leveling-up-unvanquished-0-56/

[illwieckz]

Replacement of the second drive is due soon™:

Code: Select all

92.3% done, 0 write errs, 0 uncorr. read errs

I started drafting some layout on my laptop for the linuxfr.org article. Unlike the unvanquished blog post, I want it to summarize the changes done since 0.55, since the last article there was for 0.55. I want to make the indiedb an English translation of that “from 0.55 to 0.56” retrospective. All those 0.55.x point releases were nice iterative work making 0.56 possible.

I want to make a 0.56.1 release soon, especially to ship the fix for the “flamer in your face” bug. So I'll likely submit the linuxfr.org article for review and publication after that, once the fix has shipped and be delivered, and the indiedb article would then follow.

[XReaperX]

Replacement of the second drive is due soon™:

Code: Select all

92.3% done, 0 write errs, 0 uncorr. read errs

I started drafting some layout on my laptop for the linuxfr.org article. Unlike the unvanquished blog post, I want it to summarize the changes done since 0.55, since the last article there was for 0.55. I want to make the indiedb an English translation of that “from 0.55 to 0.56” retrospective. All those 0.55.x point releases were nice iterative work making 0.56 possible.

I want to make a 0.56.1 release soon, especially to ship the fix for the “flamer in your face” bug. So I'll likely submit the linuxfr.org article for review and publication after that, once the fix has shipped and be delivered, and the indiedb article would then follow.

I thought 0.56.1 had already happened. I guess it was just a bad dream.

[illwieckz]

I thought 0.56.1 had already happened.

I meant 0.56.2.

I guess it was just a bad dream.

The bad dream would be dreaming that 0.56.1 never happened and never fixed the bug that would have discouraged players to join servers.