Bug 1045810

Summary: [abrt] systemd-204-17.fc19: journal_file_find_data_object_with_hash: Process /usr/lib/systemd/systemd-journald was killed by signal 7 (SIGBUS)
Product: [Fedora] Fedora Reporter: Radwan Yahia <radwan_b1>
Component: systemdAssignee: systemd-maint
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bugzilla.redhat, johannbg, jorti, jsynacek, lnykryn, msekleta, orti1980, plautrba, systemd-maint, tomek, vpavlin, yashperica, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/509867db705bc6956990be81f855704d263560df
Whiteboard: abrt_hash:8db36f02fcf48309106777afe15ca002ab875334
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-07 08:49:14 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 Radwan Yahia 2013-12-22 07:16:38 UTC 
Description of problem:
after re installing fedora I faced this problem.
I was thinking its HD or ram issue

Version-Release number of selected component:
systemd-204-17.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-journald
crash_function: journal_file_find_data_object_with_hash
executable:     /usr/lib/systemd/systemd-journald
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 journal_file_find_data_object_with_hash at ../src/journal/journal-file.c:803
 #1 journal_file_append_data at ../src/journal/journal-file.c:958
 #2 journal_file_append_entry at ../src/journal/journal-file.c:1336
 #3 write_to_journal at ../src/journal/journald-server.c:476
 #4 dispatch_message_real at ../src/journal/journald-server.c:682
 #5 server_dispatch_message at ../src/journal/journald-server.c:776
 #6 stdout_stream_log at ../src/journal/journald-stream.c:130
 #7 stdout_stream_line at ../src/journal/journald-stream.c:231
 #8 stdout_stream_scan at ../src/journal/journald-stream.c:261
 #9 stdout_stream_process at ../src/journal/journald-stream.c:312
Comment 1 Radwan Yahia 2013-12-22 07:16:46 UTC 
Created attachment 840271 [details]
File: backtrace
Comment 2 Radwan Yahia 2013-12-22 07:16:50 UTC 
Created attachment 840272 [details]
File: cgroup
Comment 3 Radwan Yahia 2013-12-22 07:16:52 UTC 
Created attachment 840273 [details]
File: core_backtrace
Comment 4 Radwan Yahia 2013-12-22 07:16:55 UTC 
Created attachment 840274 [details]
File: dso_list
Comment 5 Radwan Yahia 2013-12-22 07:16:57 UTC 
Created attachment 840275 [details]
File: environ
Comment 6 Radwan Yahia 2013-12-22 07:16:59 UTC 
Created attachment 840276 [details]
File: exploitable
Comment 7 Radwan Yahia 2013-12-22 07:17:04 UTC 
Created attachment 840277 [details]
File: limits
Comment 8 Radwan Yahia 2013-12-22 07:17:07 UTC 
Created attachment 840278 [details]
File: maps
Comment 9 Radwan Yahia 2013-12-22 07:17:12 UTC 
Created attachment 840279 [details]
File: open_fds
Comment 10 Radwan Yahia 2013-12-22 07:17:14 UTC 
Created attachment 840280 [details]
File: proc_pid_status
Comment 11 Radwan Yahia 2013-12-22 07:17:17 UTC 
Created attachment 840281 [details]
File: var_log_messages
Comment 12 Zbigniew Jędrzejewski-Szmek 2014-07-23 02:46:46 UTC 
Sorry for the slow response. Yes, mmaped files cause segfaults on IO. Not much we can do about this without kernel changes.
Comment 13 Lennart Poettering 2015-01-05 00:38:32 UTC 
*** Bug 1177726 has been marked as a duplicate of this bug. ***
Comment 14 Lennart Poettering 2015-01-05 00:38:49 UTC 
*** Bug 1164427 has been marked as a duplicate of this bug. ***
Comment 15 Lennart Poettering 2015-01-05 00:39:17 UTC 
*** Bug 1151848 has been marked as a duplicate of this bug. ***
Comment 16 Lennart Poettering 2015-01-05 00:39:21 UTC 
*** Bug 1098722 has been marked as a duplicate of this bug. ***
Comment 17 Lennart Poettering 2015-01-05 00:42:35 UTC 
I now added some code to journald git, that catches SIGBUS, remaps the triggering page to an anonymous page, then detects this afterwards and rotates the file away.

This should make us more robust on file systems where overwriting bytes in a file can fail due to disk full, such as COW file systems (btrfs).
Comment 18 Lennart Poettering 2015-01-05 02:35:47 UTC 
*** Bug 1053292 has been marked as a duplicate of this bug. ***
Comment 19 Jan Synacek 2015-01-07 08:49:14 UTC 
http://cgit.freedesktop.org/systemd/systemd/commit/?id=fa6ac76083b8ffc1309876459f54f9f0e2843731

This patch is nontrivial to backport, even to F20.