Notices by Peter Krefting (nafmo@social.vivaldi.net), page 5

The 6+ hours overnight memtest gave me a PASS on the new memory configuration, so now I am *copying* the files over to a new hard disk (configured as a single-disk RAID1, to be updated with the disk I'm copying *from* afterwards).

Copying 1.5 Tbyte of files does take a while (5 hours and counting so far), but since I don't trust the metadata of the old filesystem, I am not taking the chance to just have Linux RAID mirror it over.

I need to clean up the filesystem, it is heavy with backups of backups of old root filesystem copies which had backups of old machines with backups on them...

#Linux #SystemRecovery

@vingtroiseize Perfect for running https://c64online.com/c64-games/spectrum-emulator/

#Oslotrikken kjører #Linux på informasjonsskjermene sine.

Looks like it's the 2019 drive that has uncorrectable errors, while the 2016 drive is fine. Looks like I need to replace it sooner rather than later.

@nixCraft It feels like they are don't Windows app distribution (ship all libraries in the binary directory), which is one of the reasons I don't like Windows.

But... I could see how the software I write at $DAYJOB that ends up as a DEB (previously RPM) in /opt is halfway there anyway, with a slew of private, forked libraries.

Då är julsäsongen officiellt inledd
Hittade den här på #Hemköp i #Fellingsbro förra helgen. Kanske en aning tidigt med jul i september?

#Trocadero #Trocamust #Julmust

@adrinux Thanks for the pointers.

I think I will stick with something I know how to work with (ext4 or xfs over mdraid) as I have use that setup extensively both at home and at work. But if I get around to it, I might make me a toy VM to play with it a bit to learn more.

Turns out I took the wrong memory chip out. Now I have a combination of chips (including some older, smaller, ones) that earned me a "PASS" banner.

I am still going to rebuild the file system, I'm afraid there are deeper corruptions, but that will have to wait a little while. I've bought a new disk to replace the one that has been constantly-on since 2016 (the other one in the RAID is from 2019, so practically still brand-new).

The file system corruption runs deeper. After a couple of hours, the system bailed with

EXT4-fs error (device md0): ext4_lookup:1856: inode #120979457: comm updatedb.plocat: iget: bad extra_isize 9234 (inode size 256)
Aborting journal on device md0-8.
EXT4-fs error (device md0): ext4_journal_check_start:83: comm rs:main Q:Reg: Detected aborted journal
EXT4-fs error (device md0): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal
EXT4-fs (md0): Remounting filesystem read-only

which most definitely does not look good :-/

@popey I've had a few. After harddisks failing, memory chips going bad is the second most common error

I have a theory as to what is going wrong...

#linux #memtest86

Something is obviosly not right with the file system, as it has remounted itself to read-only again :-/

@adrinux Is that somehow less resilient to driver bugs/memory corruption/cosmic radiation or whatever happened (I have no idea) than mdraid+ext4?

This is the first time I have had something like this happening after running mdraid+ext4 for well over a decade on multiple machines. I have not tested zfs, so I have no point of comparison.

It's never a good sign when fsck leaves 55 Gbytes worth of files in /lost+found

I guess it doesn't help to have the file system on RAID when the logical file system structures break. Seems mostly to be backups that are affected, though, those should repair themselves on the next backup run. That and a couple of Git repositories that lost some objects and needed to be recloned from checkouts/backups.

#linux #crash #fsck

#Vivaldi releases a crap^H^H^H^H snap package of the browser.

Well, I guess maybe someone will be happy, but I am not going to touch that even with a ten-foot pole...

https://vivaldi.com/blog/vivaldi-embraces-snap/

@mihamarkic It sort of has ("git branch --edit-description"), but it needs to be shown in more places.

@Mediablikk Jepp. Etter å ha abonnert på #Dagsavisen siden cirka 2003 så sa jeg opp når de så-å-si la ned papirutgaven.

@brucelawson Absolutely! Let's all embrace the Turkish "ı" instead. And let's start using "ȷ" as well.

Can we also please get rid of extra waves, like how "w" is just two "v"s and "m" is just two "n"s?

And don't get me started on the mirroring of characters! How can one even see the differences between d, b, q, p, or between the y and the ʎ?

@karlemilnikka Interesting, maybe one should tip the Norwegian Consumer Authority about that, as they do sell these here in Norway. An unpatched security vulnerability *is* a manufacturing defect.

"The statutory warranty period depends on how long the product is meant to last when subjected to normal use. Sofas and mobile phones are examples of products with a 5-year warranty period."

https://www.forbrukerradet.no/cause-for-complaint/

If you're upset that there's a black #SpiderMan or a female #Thor, or that Ms. Marvel is #Muslim, or that Captain Marvel was pro- #feminism or any of the other things #rightwing "fans" say is "stealing their childhood" you never got it in the first place.

The stories we grew up with all taught us to value other people and cultures and to treasure the differences between us. Only villains were xenophobic, or sexist, or racist, or totalitarian. I can't understand how anyone can have missed that.