[systemd-devel] Antw: [EXT] [systemd‑devel] Q: journalctl ‑g

[Ulrich Windl]

>>> "Ulrich Windl" <Ulrich.Windl at rz.uni-regensburg.de> schrieb am 04.03.2022
um
08:07 in Nachricht <6221BAC1020000A10004867F at gwsmtp.uni-regensburg.de>:
> Hi!
> 
> In SLES15 SP3 (systemd‑246.16‑7.33.1.x86_64) I have this effect, wondering 
> whether it is a bug or a feature:
> When using "journalctl ‑b ‑g raid" I see that _ome_ matches are highlighted
in 

s/_ome_/_some_/; # Sorry

> red, but others aren't. For example:
> Mar 01 01:37:09 h16 kernel: mega*raid*_sas 0000:c1:00.0: BAR:0x1  BAR's 
> base_addr(phys):0x00000000a5500000  mapped virt_addr:0x00000000ae628322
> Mar 01 01:37:09 h16 kernel: megaraid_sas 0000:c1:00.0: FW now in Ready
state
> ...
> 
> That means in the line following the raid is not highlighted, even though it

> matched obviously.
> Likewise any further "megaraid_sas" aren't highlighted.
> 
> But also those are not highlighted:
> Mar 01 01:37:20 h16 kernel: raid6: avx2x4   gen() 16182 MB/s
> 
> Mar 01 01:37:47 h16 kernel: md/raid1:md127: active with 2 out of 2 mirrors
> 
> Mar 01 01:37:48 h16 smartd[5871]: Device: /dev/bus/0 [megaraid_disk_00], 
> type changed from 'megaraid,0' to 'sat+megaraid,0'
> 
> But here it is highlighted again:
> Mar 01 01:38:55 h16 pacemaker‑controld[7236]:  notice: Requesting local 
> execution of probe operation for prm_lockspace_*raid*_md10 on h16
> Mar 01 01:38:55 h16 pacemaker‑controld[7236]:  notice: Result of probe 
> operation for prm_lockspace_*raid*_md10 on h16: not running
> 
> And this, too:
> Mar 01 07:58:44 h16 kernel: mega*raid*_sas 0000:c1:00.0: Firmware crash dump

> is not available
> Mar 01 08:00:47 h16 supportconfig[671]: Software *Raid*...
> 
> And this not:
> Mar 02 03:07:48 h16 smartd[5871]: Device: /dev/bus/0 [megaraid_disk_00] 
> [SAT], starting scheduled Short Self‑Test.
> 
> Regards,
> Ulrich