Bug 1112874
| Summary: | [abrt] btrfs-progs: __free_extent(): btrfsck killed by SIGABRT | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Spenk <henk.spaan> | ||||||||||||||||||||||
| Component: | btrfs-progs | Assignee: | Josef Bacik <josef> | ||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||
| Version: | 20 | CC: | esandeen, josef, mmahut, sweil | ||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/258ec6b82aadb94b4cc186008ba94b75a035d467 | ||||||||||||||||||||||||
| Whiteboard: | abrt_hash:386bfb275c9907a3c7408f5e3e63172bb772c2cc | ||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||
| Last Closed: | 2015-06-29 21:18:38 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
Spenk
2014-06-24 22:13:22 UTC
Created attachment 911889 [details]
File: backtrace
Created attachment 911890 [details]
File: cgroup
Created attachment 911891 [details]
File: core_backtrace
Created attachment 911892 [details]
File: dso_list
Created attachment 911893 [details]
File: environ
Created attachment 911894 [details]
File: limits
Created attachment 911895 [details]
File: maps
Created attachment 911896 [details]
File: open_fds
Created attachment 911897 [details]
File: proc_pid_status
Created attachment 911898 [details]
File: var_log_messages
> #4 __free_extent at extent-tree.c:2335 > Created attachment 911889 [details] > File: backtrace #3 0x0000003b2e82ec42 in __GI___assert_fail (assertion=assertion@entry=0x458fd0 "!(owner_objectid != btrfs_tree_block_level(leaf, bi))", file=file@entry=0x45910d "extent-tree.c", line=line@entry=2335, function=function@entry=0x459447 <__PRETTY_FUNCTION__.8874> "__free_extent") at assert.c:101 This comes from the WARN_ON() in: if (owner_objectid < BTRFS_FIRST_FREE_OBJECTID && key.type == BTRFS_EXTENT_ITEM_KEY) { struct btrfs_tree_block_info *bi; BUG_ON(item_size < sizeof(*ei) + sizeof(*bi)); bi = (struct btrfs_tree_block_info *)(ei + 1); WARN_ON(owner_objectid != btrfs_tree_block_level(leaf, bi)); } Which comes from the depth of time in btrfs-progs and is still present upstream. commit 95d3f20b51e9b2ee21822313ad4f31279396407b Author: Chris Mason <chris.mason> Date: Fri May 29 16:35:30 2009 -0400 Mixed back reference (FORWARD ROLLING FORMAT CHANGE) It's a simple on-disk inconsistency (the caller's owner of the ref doesn't match what's on disk) that causes fsck to explode. Those playing along at home can be forgiven for confusing WARN_ON() with something that issues a warning. It's a hard assertion. $ grep _ON kerncompat.h #define BUG_ON(c) assert(!(c)) #define WARN_ON(c) assert(!(c)) Hmm, Trying to scrub also results in a report, but I've got a tainted kernel (nvidia), so I can report using the reporting tool. After the report the process still seems to be running though and the cancel command keeps hanging without a response. After reboot, the process seems to kill after five kerneloops according to cancel command, but running state is not cleared as the process according to the start command. I'll wait for version 3.15 to appear in updates. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |