Mark Nowiasz

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

Nerd, interested in lot of stuff. Usually posts bilingual and uses categories (deutsch, english)

Ort:: 13435 Berlin

Berlin

Germany

Heimatstadt:: Castrop-Rauxel

Geschlecht:: Männlich

Status:: Single

Homepage:: https://mark.nowiasz.de/

btrfs rules :-)

Mon, 03 Feb 2020 06:53:49 +0100

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

Ich nutze schon seit Jahren praktisch überall btrfs und es gab so gut wie nie Schwierigkeiten, im Gegenteil: Es hat mir mehrfach den Hintern gerettet. Zuletzt am Samstag. Ich lasse - wie empfohlen - regelmäßig btrfs scrub laufen. btrfs scrub überprüft sämtliche Checksummen (Dateien, Metadaten) und erkennt dann falls Bit rot aufgereten ist. Genau das ist am Samstag passiert:

scrub device /dev/mapper/crbackup (id 1) history
Scrub started:    Sat Feb  1 00:00:09 2020
Status:           finished
Duration:         5:20:51
Total to scrub:   1.63TiB
Rate:             75.15MiB/s
Error summary:    csum=256
  Corrected:      0
  Uncorrectable:  256
  Unverified:     0

Glücklicherweise sind nur eher unwichtige Datein Backupbetroffen, nämlich systemd-journals:

[1061203.625001] BTRFS warning (device dm-3): checksum error at logical 22266249216 on dev /dev/mapper/crbackup, physical 23348379648, root 14466, inode 6257873, offset 71372800, length 4096, links 1 (path: var/log/journal/ea31f7c7a00d9c85d020e2475ba79427/system@205f60a021bb49848e1bfd0d90a5b20b-000000000093d480-000590ce96ca6d78.journal)

Unter einem konventionellen Dateisystem wie ext4 gibt es keine Chance solche Probleme zu entdecken. Ich weiß schon warum ich nie wieder ext4 & co einsetzen möchte :-)

#btrfs #linux

deutsch english Linux

HTPC auf systemd umgestellt / Converted my HTPC to systemd

Sun, 27 Jan 2019 16:25:54 +0100

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

Heute endlich durchgeführt was ich schon seit längerer Zeit durchführen wollte, aber nie die Zeit dafür (genommen) habe: Den HTPC mit Kodi, tvheadend, oscam & co von openrc auf systemd umgestellt. Das war damit das letzte System von mir was noch sysv-init / openrc hatte. Lief problemlos, und das Teil startet nun wesentlich schneller :-)

#gentoo #linux

deutsch Linux englisch

show all 10 comments

Sun, 27 Jan 2019 17:46:36 +0100

Cindy Brown

browneyedgirl@pluspora.com

I am so, so sorry.

Sun, 27 Jan 2019 18:26:01 +0100

tvannahl@pluspora.com

First time user or are you already familiar with the basics and concepts?

Sun, 27 Jan 2019 18:35:03 +0100

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

@tvannahl@pluspora.com I'm already using systemd for years now - the HTPC was the only machine still running a classic init system, and you know, never change a running system.. but today I've finally found the time (and energy) to switch, now all my Gentoo boxes are using systemd :-)

Mon, 28 Jan 2019 13:44:26 +0100

cb7f604332cf39

cb7f604332cf39@hubzilla.eu

Right now I switch all my systems back to Sys5 init, cause of systemd discussions in Debian maintenance.
Switch to Devuan.

Mon, 28 Jan 2019 14:58:20 +0100

tvannahl@pluspora.com

@Mark Nowiasz has the process of switching from sys5 to systemd in gentoo been enhanced in the last years? The last time I've done it there was a considerable amount of work involed.

If @Mark Nowiasz doesn't mind, I would like to ask @cb7f604332cf39 for a reference to the discussion he mentioned, but only if @Mark Nowiasz wouldn't feel this thread to be hijacked. While I would not want to switch to the older concepts of sys5, I am interessted in technical issues others have with systemd. For me the introduction of systemd has, after diving into the topic and consulting the documentation, increased the productivity of my adminstrative and development processes.

Mon, 28 Jan 2019 15:04:30 +0100

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

@tvannahl@pluspora.com Well, it went qujite smooth - but of course, you have to consider that I've setup some new Gentoo servers (also using systemd) in the past month, so I had some experience :-) I think Gentoo's guide is rather good: https://wiki.gentoo.org/wiki/Systemd but as I said - I'm quite experienced in running Gentoo using systemd :-)

Feel free to "hijack" the thread :-D

Mon, 28 Jan 2019 15:25:18 +0100

cb7f604332cf39

cb7f604332cf39@hubzilla.eu

yeah, ok - thanks Mark.
I don't want to start a flamewar - I'm getting too old for this.

Parts of the discussion happens here:
http://forums.debian.net/viewtopic.php&t=139950&start=0

and here:
https://www.reddit.com/r/linux/comments/agna5n/debian_systemd/maintainer_steps_down_over/

Lot's of stuff to read.
In between: the systemd bugs are fixed.
Less new pro's and con's.

I heared some rumors that Lennart should have said somethning like:
- systemd tools are getting to complex for him alone
- less resources - Lennart calls for other developers to participate

Please take it really as rumors, cause I can't find the lines again.

And this reminds me of the pulseaudio project where Lennart was also project lead and how it went/died.
Looks like that he's not an easy kind of developer.

Everybody should make her/his own decision.

Mon, 28 Jan 2019 16:17:42 +0100

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

@cb7f604332cf39 Oh, you mean a holy war, not a flame war ;-)

Well, I'm getting to old for this, too. Just let me tell you why I'm using systemd. Some time ago I was totally against it, thankfully #gentoo had/has the option to choose between systemd and openrc (the best SysV-init system I know). Then I was setting up those two Gentoo servers and I was thinking that - despite all my misgivings - systemd seems to the future, why bother setting them up with openrc if I have to change it to systemd sooner or later?

So I set them up, grew accustomed to systemd - and started to really like it, now I don't want a SysV init system anymore, so you call me a convert :-)

However: I really appreciate #gentoo for maintaining two different set of init systems - and having the freedom of choice. After all, that's what Linux is about, isn't it? So if you prefer SysV init, that's totally cool with me.

Mon, 28 Jan 2019 17:02:23 +0100

cb7f604332cf39

cb7f604332cf39@hubzilla.eu

You're more modern than I'm. :thumbsup:
I prefer the old scool kiss prinicipal.

I don't need the operating systems like:
- emacs
- chromeos
or systemd

sorry for the flat joke.

Mon, 28 Jan 2019 18:48:36 +0100

tvannahl@pluspora.com

Thank you for the references @cb7f604332cf39 :-)

Garantierter Neustart via remote

Mon, 15 Oct 2018 09:20:22 +0200

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

Und wieder was Neues gelernt: Was macht man wenn (remote) shutdown -r (oder halt -f) nicht funktioniert, weil sich irgendwas IO technisch verklemmt hat? Die Anwort: via simulierten Reset-Knopf:

echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger

Hat funktioniert :-)

Linux

Mon, 15 Oct 2018 20:44:28 +0200

Markus Birth

mbirth@hub.netzgemeinde.eu

Ähhh ... was ist daraus geworden?

* Raising
* Elephants
* Is
* So
* Utterly
* Boring

… also zumindest S (Sync) und U (Remount r/o) hätte ich vor dem B noch abgesetzt. ;)

Mon, 15 Oct 2018 20:54:31 +0200 zuletzt bearbeitet: Mon, 15 Oct 2018 20:54:58 +0200

Mark Nowiasz

buckaroo@hub.netzgemeinde.eu

Ach was, ich habe manuell die MySQL heruntergefahren, das hat als Vorsichtsmaßnahme gereicht. Und der Rest hätte die Gefahr beinhaltet die aktiven ssh-Verbindungen abzuschließen (inklusive des Daemons). Und das System muss sowas abkönnen, schließlich kann ein Stromausfall jederzeit passieren. Und btrfs ist robust.