Version-Release number of selected component: systemd-215-19.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: journalctl _UID=1001 -b crash_function: generic_array_bisect.lto_priv.166 executable: /usr/bin/journalctl kernel: 3.17.0-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (8 frames) #0 generic_array_bisect.lto_priv.166 at ../src/journal/journal-file.c:1631 #1 generic_array_bisect_plus_one.lto_priv.167 at ../src/journal/journal-file.c:1746 #2 journal_file_move_to_entry_by_offset_for_data at ../src/journal/journal-file.c:2125 #3 next_for_match at ../src/journal/sd-journal.c:584 #8 next_with_matches.lto_priv.164 at ../src/journal/sd-journal.c:812 #9 next_beyond_location at ../src/journal/sd-journal.c:830 #10 real_journal_next.lto_priv.184 at ../src/journal/sd-journal.c:887 #11 sd_journal_next at ../src/journal/sd-journal.c:924
Are there any disk read errors present in the logs?
No errors in logs or in the filesystem: $ btrfs dev stats / [/dev/dm-0].write_io_errs 0 [/dev/dm-0].read_io_errs 0 [/dev/dm-0].flush_io_errs 0 [/dev/dm-0].corruption_errs 0 [/dev/dm-0].generation_errs 0 (it's btrfs over dm-crypt on samsung ssd 830).
Is this repeatable? systemd-216-4 might improve things.
*** This bug has been marked as a duplicate of bug 1151848 ***