Bug 1098722

Summary: [abrt] systemd: link_entry_into_array(): systemd-journald killed by SIGBUS
Product: [Fedora] Fedora Reporter: orti1980 <orti1980>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: johannbg, lnykryn, martin, msekleta, plautrba, s, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7535bc5d47b564470c24c8ffb22c72a2204f74e3
Whiteboard: abrt_hash:d9c6717ec5fbaf787bd7dfa6621b53309febc701
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-05 00:39:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description orti1980 2014-05-17 17:38:22 UTC 
Version-Release number of selected component:
systemd-208-16.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: link_entry_into_array
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.14.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 link_entry_into_array at ../src/journal/journal-file.c:1094
 #1 link_entry_into_array_plus_one at ../src/journal/journal-file.c:1164
 #2 journal_file_link_entry_item at ../src/journal/journal-file.c:1188
 #3 journal_file_link_entry at ../src/journal/journal-file.c:1229
 #4 journal_file_append_entry_internal at ../src/journal/journal-file.c:1272
 #5 journal_file_append_entry at ../src/journal/journal-file.c:1354
 #6 write_to_journal at ../src/journal/journald-server.c:460
 #7 dispatch_message_real at ../src/journal/journald-server.c:789
 #8 server_dispatch_message at ../src/journal/journald-server.c:889
 #9 server_process_syslog_message at ../src/journal/journald-syslog.c:407
Comment 1 orti1980 2014-05-17 17:38:28 UTC 
Created attachment 896617 [details]
File: backtrace
Comment 2 orti1980 2014-05-17 17:38:30 UTC 
Created attachment 896618 [details]
File: cgroup
Comment 3 orti1980 2014-05-17 17:38:32 UTC 
Created attachment 896619 [details]
File: core_backtrace
Comment 4 orti1980 2014-05-17 17:38:34 UTC 
Created attachment 896620 [details]
File: dso_list
Comment 5 orti1980 2014-05-17 17:38:36 UTC 
Created attachment 896621 [details]
File: environ
Comment 6 orti1980 2014-05-17 17:38:38 UTC 
Created attachment 896622 [details]
File: exploitable
Comment 7 orti1980 2014-05-17 17:38:40 UTC 
Created attachment 896623 [details]
File: limits
Comment 8 orti1980 2014-05-17 17:38:42 UTC 
Created attachment 896624 [details]
File: maps
Comment 9 orti1980 2014-05-17 17:38:44 UTC 
Created attachment 896625 [details]
File: open_fds
Comment 10 orti1980 2014-05-17 17:38:46 UTC 
Created attachment 896626 [details]
File: proc_pid_status
Comment 11 orti1980 2014-05-17 17:38:49 UTC 
Created attachment 896627 [details]
File: var_log_messages
Comment 12 Martin Dengler 2014-08-24 23:07:34 UTC 
Another user experienced a similar problem:

Again, similar issue (#1053292): not sure if I was trying to restart systemd-journald or just using it.  I suspect the root cause was the btrfs device that the journal was on was full (btrfs root fs & /var device was full: "btrfs fi show" showed the devid's "used" amount the same as the "size" amount).

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: link_entry_into_array
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.15.7-200.fc20.x86_64
package:        systemd-208-21.fc20
reason:         systemd-journald killed by SIGBUS
runlevel:       3 5
type:           CCpp
uid:            0
Comment 13 Lennart Poettering 2015-01-05 00:39:21 UTC 

*** This bug has been marked as a duplicate of bug 1045810 ***