Reartes Guillermo
2013-Jan-14 07:11 UTC
kernel call trace when deleting a huge file (which used all the space) with btrfs
Hi, i recently subscribed to this mailing list. Recently i have found some issues with BTRFS, i am using F18. I installed F18 in a kvm guest. What i found is: * Intermittent ENOSPC when writing after erasing a file which lead to a true ENOSPC (reported https://bugzilla.redhat.com/show_bug.cgi?id=894837) I reproduced this only in the disk i used to install F18 (/ and /boot subvols). * Kernel Call Traces when deleting a file that was written previously and used all the space. (So there was a true ENOSPC). I reproduce these on an additional disk i added to the guest (41gb). I am not getting transient ENOSPC on that disk. Jan 13 22:17:21 localhost kernel: [18160.215176] ------------[ cut here ]------------ Jan 13 22:17:21 localhost kernel: [18160.215223] WARNING: at fs/btrfs/extent-tree.c:6323 btrfs_alloc_free_block+0x376/0x380 [btrfs]() Jan 13 22:17:21 localhost kernel: [18160.215226] Hardware name: Bochs Jan 13 22:17:21 localhost kernel: [18160.215228] Modules linked in: fuse 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 iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter bnep bluetooth ebtables rfkill ip6table_filter ip6_tables 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 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm 8139too snd_page_alloc snd_timer snd 8139cp soundcore i2c_piix4 i2c_core mii virtio_balloon vhost_net tun macvtap macvlan kvm_amd kvm uinput btrfs libcrc32c zlib_deflate Jan 13 22:17:21 localhost kernel: [18160.215293] Pid: 28225, comm: rm Tainted: G W 3.6.10-4.fc18.x86_64 #1 Jan 13 22:17:21 localhost kernel: [18160.215296] Call Trace: Jan 13 22:17:21 localhost kernel: [18160.215307] [<ffffffff8105c8df>] warn_slowpath_common+0x7f/0xc0 Jan 13 22:17:21 localhost kernel: [18160.215313] [<ffffffff8105c93a>] warn_slowpath_null+0x1a/0x20 Jan 13 22:17:21 localhost kernel: [18160.215340] [<ffffffffa0031a06>] btrfs_alloc_free_block+0x376/0x380 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215375] [<ffffffffa005dc23>] ? read_extent_buffer+0xc3/0x120 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215401] [<ffffffffa001da9a>] __btrfs_cow_block+0x12a/0x510 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215427] [<ffffffffa001df77>] btrfs_cow_block+0xf7/0x200 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215453] [<ffffffffa00221a7>] btrfs_search_slot+0x3e7/0x8f0 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215459] [<ffffffff810f1107>] ? call_rcu_sched+0x17/0x20 Jan 13 22:17:21 localhost kernel: [18160.215488] [<ffffffffa003737f>] btrfs_del_csums+0x12f/0x310 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215516] [<ffffffffa002b059>] __btrfs_free_extent+0x679/0x800 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215561] [<ffffffffa002f526>] run_clustered_refs+0x316/0xb50 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215594] [<ffffffffa007c3a3>] ? find_ref_head+0x83/0xf0 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215622] [<ffffffffa002fe48>] btrfs_run_delayed_refs+0xe8/0x2e0 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215654] [<ffffffffa00420f1>] __btrfs_end_transaction+0xf1/0x3a0 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215685] [<ffffffffa0042415>] btrfs_end_transaction+0x15/0x20 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215717] [<ffffffffa004c440>] btrfs_evict_inode+0x200/0x310 [btrfs] Jan 13 22:17:21 localhost kernel: [18160.215730] [<ffffffff811aa6b2>] evict+0xa2/0x1a0 Jan 13 22:17:21 localhost kernel: [18160.215735] [<ffffffff811aae73>] iput+0x103/0x190 Jan 13 22:17:21 localhost kernel: [18160.215742] [<ffffffff8119e51f>] do_unlinkat+0x15f/0x1a0 Jan 13 22:17:21 localhost kernel: [18160.215749] [<ffffffff810d8d5c>] ? __audit_syscall_entry+0xcc/0x300 Jan 13 22:17:21 localhost kernel: [18160.215756] [<ffffffff81627045>] ? do_async_page_fault+0x35/0x90 Jan 13 22:17:21 localhost kernel: [18160.215762] [<ffffffff811a0dab>] sys_unlinkat+0x1b/0x50 Jan 13 22:17:21 localhost kernel: [18160.215767] [<ffffffff8162bae9>] system_call_fastpath+0x16/0x1b Jan 13 22:17:21 localhost kernel: [18160.215771] ---[ end trace 54a02fbdc3904cff ]--- Jan 13 22:17:21 localhost kernel: [18160.218829] ------------[ cut here ]------------ I get many of those on sdb1, and the transient ENOSPC on sda2 Thanks in advance. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Chris Murphy
2013-Jan-14 15:25 UTC
Re: kernel call trace when deleting a huge file (which used all the space) with btrfs
On Jan 14, 2013, at 12:11 AM, Reartes Guillermo <rtguille@gmail.com> wrote:> > > Recently i have found some issues with BTRFS, i am using F18.For list reference, Fedora 18 ships with btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18, and kernel-3.6.10-4.fc18.x86_64, which is what your bug report shows. Is this reproducible with either kernel-3.7.2-201.fc18 or kernel-3.8.0-0.rc3.git0.1.fc19? Both are in koji. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Reartes Guillermo
2013-Jan-15 01:13 UTC
Re: kernel call trace when deleting a huge file (which used all the space) with btrfs
I am afraid it is reproducible with kernel 3.7.2-201.fc18.x86_64, with the same procedure. Cheers. On Mon, Jan 14, 2013 at 12:25 PM, Chris Murphy <lists@colorremedies.com> wrote:> > On Jan 14, 2013, at 12:11 AM, Reartes Guillermo <rtguille@gmail.com> > wrote: > >> >> >> Recently i have found some issues with BTRFS, i am using F18. > > > For list reference, Fedora 18 ships with > btrfs-progs-0.20.rc1.20121017git91d9eec-1.fc18, and > kernel-3.6.10-4.fc18.x86_64, which is what your bug report shows. > > Is this reproducible with either kernel-3.7.2-201.fc18 or > kernel-3.8.0-0.rc3.git0.1.fc19? Both are in koji. > > > Chris Murphy-- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html