Bug 893690 - [abrt]: WARNING: at fs/btrfs/tree-log.c:3819 btrfs_log_inode_parent+0x3f8/0x450 [btrfs]()
Summary: [abrt]: WARNING: at fs/btrfs/tree-log.c:3819 btrfs_log_inode_parent+0x3f8/0x4...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zach Brown
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:baa3c676c57114e2c887e47cdc7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-09 17:54 UTC by Kevin Fenzi
Modified: 2015-05-18 01:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 20:34:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kevin Fenzi 2013-01-09 17:54:10 UTC
Description of problem:
Normal use, no ill effects, just the btrfs warning. 

I do have a cron job that takes hourly snapshots and keeps 8 of them around. It may have happened at snapshot time.

Additional info:
WARNING: at fs/btrfs/tree-log.c:3819 btrfs_log_inode_parent+0x3f8/0x450 [btrfs]()
Hardware name: 4384FM4
Modules linked in: cpufreq_stats ebtable_nat xt_CHECKSUM bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter rfcomm ip6_tables bnep be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media btusb bluetooth arc4 snd_hda_codec_hdmi snd_hda_codec_conexant iTCO_wdt iTCO_vendor_support iwldvm mac80211 coretemp snd_hda_intel microcode snd_hda_codec snd_hwdep snd_seq snd_seq_device vhost_net snd_pcm tun macvtap macvlan iwlwifi kvm_intel i2c_i801 kvm lpc_ich snd_page_alloc intel_ips mfd_core thinkpad_acpi cfg80211 snd_timer e1000e mei snd uinput soundcore rfkill btrfs zlib_deflate libcrc32c dm_crypt crc32c_intel i915 ghash_clmulni_intel i2c_algo_bit drm_kms_helper firewire_ohci sdhci_pci drm sdhci firewire_core mmc_core crc_itu_t i2c_core mxm_wmi video wmi
Pid: 18394, comm: local Not tainted 3.8.0-0.rc2.git2.2.fc19.x86_64 #1
Call Trace:
 [<ffffffff8105e5af>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff8105e60a>] warn_slowpath_null+0x1a/0x20
 [<ffffffffa020f2b8>] btrfs_log_inode_parent+0x3f8/0x450 [btrfs]
 [<ffffffffa020f357>] btrfs_log_dentry_safe+0x47/0x70 [btrfs]
 [<ffffffffa01e60e7>] btrfs_sync_file+0x167/0x230 [btrfs]
 [<ffffffff811cb88d>] do_fsync+0x5d/0x90
 [<ffffffff811cbb00>] sys_fsync+0x10/0x20
 [<ffffffff8165a099>] system_call_fastpath+0x16/0x1b

Comment 1 Fedora End Of Life 2013-04-03 18:05:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Jeffrey C. Ollie 2013-04-08 15:08:48 UTC
Seeing this on F18 kernel 3.8.5-201.fc18.x86_64

Comment 3 Josh Boyer 2013-09-18 20:55:53 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Josef Bacik 2013-09-23 20:34:45 UTC
Fixed in 3.10.


Note You need to log in before you can comment on or make changes to this bug.