<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">A SLES15 SP6 machine running in VMware recently showed severe I/O hangs (which seem to be related to Veam backup software making snapshots when also VMware snapshots of the VM exist).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The point was that even direct reads were hanging for about three minutes until the kernel logged a “kernel: sd 0:0:1:0: [sdb] tag#801 task abort on host 0, 00000000aade996c”.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">So most likely the read would not provide any data while the write would not have stored any.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In that context I noticed journald dumping core like this:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 kernel: sd 0:0:1:0: [sdb] tag#217 task abort on host 0, 000000004f9d9a0f<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: Finished User Runtime Directory /run/user/0.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: Starting User Manager for UID 0...<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: Process 747 (systemd-journal) of user 0 dumped core.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.54731128d84044c8922ec7e1e329e024.747.1740467><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: Stack trace of thread 747:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #0 0x00007fe837923f3a fsync (libc.so.6 + 0x123f3a)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #1 0x00007fe837e5bda3 n/a (libsystemd-shared-254.so + 0x25bda3)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #2 0x00007fe837e5ead5 journal_file_append_object (libsystemd-shared-254.so + 0x25ead5)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #3 0x00007fe837e63c3e n/a (libsystemd-shared-254.so + 0x263c3e)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #4 0x00007fe837e64675 journal_file_append_entry (libsystemd-shared-254.so + 0x264675)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #5 0x00005582df343506 n/a (systemd-journald + 0x10506)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #6 0x00005582df355306 n/a (systemd-journald + 0x22306)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #7 0x00005582df34711c n/a (systemd-journald + 0x1411c)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #8 0x00007fe837e88674 n/a (libsystemd-shared-254.so + 0x288674)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #9 0x00007fe837e88941 sd_event_dispatch (libsystemd-shared-254.so + 0x288941)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #10 0x00007fe837e89208 sd_event_run (libsystemd-shared-254.so + 0x289208)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #11 0x00005582df33b98d n/a (systemd-journald + 0x898d)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #12 0x00007fe837840e6c __libc_start_call_main (libc.so.6 + 0x40e6c)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #13 0x00007fe837840f35 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x40f35)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: #14 0x00005582df33bbe1 n/a (systemd-journald + 0x8be1)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd-coredump[24229]: ELF object binary architecture: AMD x86-64<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: systemd-journald.service: Failed with result 'watchdog'.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: systemd-journald.service: Consumed 2.973s CPU time.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: Started User Manager for UID 0.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 25 08:03:30 v04 systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The point is: Is it expected that journald aborts this way, or is it considered to be a bug? Version was systemd-254.23-150600.4.25.1.x86_64<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Ulrich<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>