Re: btrfs_destroy_inode WARN_ON.
On Mon, Mar 28, 2016 at 04:14:46PM +0200, Markus Trippelsdorf wrote: > On 2016.03.28 at 10:05 -0400, Josef Bacik wrote: > > >Mar 24 10:37:27 x4 kernel: WARNING: CPU: 3 PID: 11838 at > > >fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x22b/0x2a0 > > > > I saw this running some xfstests on our internal kernels but haven't been > > able to reproduce it on my latest enospc work (which is obviously perfect). > > What were you doing when you tripped this? I'd like to see if I actually > > did fix it or if I still need to run it down. Thanks, > > I cannot really tell. Looking at the backtrace, both Dave and I were > running rm. > This warning happened just once on my machine, so the issue is obviously > very hard to trigger. On the other hand, it seems to be triggering really often (on the order of ~10 mins of light use) on my box. I understandably ran away from 4.6-rc to stable kernels (no one likes to risk data loss), but even in that little time it triggered 328 times (over ~20ish boots). Despite all of these WARNs, there's no data loss yet on the disk in question, and the filesystem appears consistent. Call stacks show a variety of callers of btrfs_destroy_inode, originating from do_unlinkat, SyS_rename, btrfs_ioctl_snap_destroy, shrink_zone, or task_work_run, direct callers being: do_unlinkat __dentry_kill dput __dentry_kill shrink_dentry_list dispose_list prune_icache_sb Just tried 4.6-rc5, it's still there. Any way I could help debug this? -- A tit a day keeps the vet away. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs_destroy_inode WARN_ON.
On Fri, Apr 01, 2016 at 02:12:27PM -0400, Dave Jones wrote: > BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 30s! > Showing busy workqueues and worker pools: > workqueue events: flags=0x0 > pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/256 > pending: vmstat_shepherd > pwq 4: cpus=2 node=0 flags=0x0 nice=0 active=1/256 > pending: check_corruption > pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=3/256 > pending: usb_serial_port_work, lru_add_drain_per_cpu BAR(17230), > e1000_watchdog_task > workqueue events_power_efficient: flags=0x82 > pwq 8: cpus=0-3 flags=0x4 nice=0 active=3/256 > pending: fb_flashcursor, neigh_periodic_work, neigh_periodic_work > workqueue events_freezable_power_: flags=0x86 > pwq 8: cpus=0-3 flags=0x4 nice=0 active=1/256 > pending: disk_events_workfn > workqueue netns: flags=0x6000a > pwq 8: cpus=0-3 flags=0x4 nice=0 active=1/1 > in-flight: 10038:cleanup_net > workqueue writeback: flags=0x4e > pwq 8: cpus=0-3 flags=0x4 nice=0 active=2/256 > pending: wb_workfn, wb_workfn > workqueue kblockd: flags=0x18 > pwq 3: cpus=1 node=0 flags=0x0 nice=-20 active=2/256 > pending: blk_mq_timeout_work, blk_mq_timeout_work > workqueue vmstat: flags=0xc > pwq 4: cpus=2 node=0 flags=0x0 nice=0 active=1/256 > pending: vmstat_update > pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256 > pending: vmstat_update > pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 > pending: vmstat_update > pool 8: cpus=0-3 flags=0x4 nice=0 hung=0s workers=11 idle: 11638 10276 609 > 17937 606 9237 605 891 15998 14100 > note: trinity-c13[18815] exited with preempt_count 1 This has wedged userspace too: 23082 pts/2SN+0:00 | \_ /bin/bash scripts/test-multi.sh 14140 pts/2SNL+ 0:15 | \_ ../trinity -q -l off -N 100 -a64 -x fsync -x fdatasync 16900 ?DNs0:04 | \_ ../trinity -q -l off -N 100 -a64 -x fsync -x fdata 18894 ?DNs0:02 | \_ ../trinity -q -l off -N 100 -a64 -x fsync -x fdata (14:16:02:davej@think:trinity[master])$ stack 16900 [] wait_on_page_bit_killable+0x156/0x1b0 [] __lock_page_or_retry+0x112/0x1b0 [] filemap_fault+0x367/0xb30 [] __do_fault+0x167/0x3d0 [] handle_mm_fault+0x1837/0x2520 [] __do_page_fault+0x248/0x770 [] do_page_fault+0x39/0xa0 [] page_fault+0x1f/0x30 [] mm_release+0x1ec/0x230 [] do_exit+0x5d0/0x18c0 [] do_group_exit+0xac/0x190 [] get_signal+0x48f/0xeb0 [] do_signal+0xa0/0xb50 [] exit_to_usermode_loop+0xd9/0x100 [] do_syscall_64+0x238/0x2b0 [] return_from_SYSCALL_64+0x0/0x7a [] 0x (14:16:09:davej@think:trinity[master])$ stack 18894 [] btrfs_file_write_iter+0xe8/0x9a0 [btrfs] [] __vfs_write+0x279/0x2e0 [] vfs_write+0x11e/0x2b0 [] SyS_write+0xd2/0x1a0 [] do_syscall_64+0x103/0x2b0 [] return_from_SYSCALL_64+0x0/0x7a [] 0x I tried to ftrace the latter process, and the box completely hung. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs_destroy_inode WARN_ON.
On Sun, Mar 27, 2016 at 09:14:00PM -0400, Dave Jones wrote: > > WARNING: CPU: 2 PID: 32570 at fs/btrfs/inode.c:9261 > btrfs_destroy_inode+0x389/0x3f0 [btrfs] > > CPU: 2 PID: 32570 Comm: rm Not tainted 4.5.0-think+ #14 > > c039baf9 ef721ef0 88025966fc08 8957bcdb > > 88025966fc50 890b41f1 > > 88045d918040 242d4eed6048 88024eed6048 88024eed6048 > > Call Trace: > > [] ? btrfs_destroy_inode+0x389/0x3f0 [btrfs] > > [] dump_stack+0x68/0x9d > > [] __warn+0x111/0x130 > > [] warn_slowpath_null+0x1d/0x20 > > [] btrfs_destroy_inode+0x389/0x3f0 [btrfs] > > [] destroy_inode+0x67/0x90 > > [] evict+0x1b7/0x240 > > [] iput+0x3ae/0x4e0 > > [] ? dput+0x20e/0x460 > > [] do_unlinkat+0x256/0x440 > > [] ? do_rmdir+0x350/0x350 > > [] ? syscall_trace_enter_phase1+0x87/0x260 > > [] ? enter_from_user_mode+0x50/0x50 > > [] ? __lock_is_held+0x25/0xd0 > > [] ? mark_held_locks+0x22/0xc0 > > [] ? syscall_trace_enter_phase2+0x12d/0x3d0 > > [] ? SyS_rmdir+0x20/0x20 > > [] SyS_unlinkat+0x1b/0x30 > > [] do_syscall_64+0xf4/0x240 > > [] entry_SYSCALL64_slow_path+0x25/0x25 > > ---[ end trace a48ce4e6a1b5e409 ]--- > > > > That's WARN_ON(BTRFS_I(inode)->csum_bytes); > > > > *maybe* it's a bad disk, but there's no indication in dmesg of anything > awry. > > Spinning rust on SATA, nothing special. > > Same WARN_ON is reachable from umount too.. > > WARNING: CPU: 2 PID: 20092 at fs/btrfs/inode.c:9261 > btrfs_destroy_inode+0x40c/0x480 [btrfs] > CPU: 2 PID: 20092 Comm: umount Tainted: GW 4.5.0-think+ #1 > a32c482b 8803cd187b60 9d63af84 > c05c5e40 c04d316c > 8803cd187ba8 9d0c4c27 880460d80040 242dcd187bb0 > Call Trace: > [] dump_stack+0x95/0xe1 > [] ? btrfs_destroy_inode+0x40c/0x480 [btrfs] > [] __warn+0x147/0x170 > [] warn_slowpath_null+0x31/0x40 > [] btrfs_destroy_inode+0x40c/0x480 [btrfs] > [] ? btrfs_test_destroy_inode+0x40/0x40 [btrfs] > [] destroy_inode+0x77/0xb0 > [] evict+0x20e/0x2c0 > [] dispose_list+0x70/0xb0 > [] evict_inodes+0x26f/0x2c0 > [] ? inode_add_lru+0x60/0x60 > [] ? fsnotify_unmount_inodes+0x215/0x2c0 > [] generic_shutdown_super+0x76/0x1c0 > [] kill_anon_super+0x29/0x40 > [] btrfs_kill_super+0x31/0x130 [btrfs] > [] deactivate_locked_super+0x6f/0xb0 > [] deactivate_super+0x99/0xb0 > [] cleanup_mnt+0x70/0xd0 > [] __cleanup_mnt+0x1b/0x20 > [] task_work_run+0xef/0x130 > [] exit_to_usermode_loop+0xf9/0x100 > [] do_syscall_64+0x238/0x2b0 > [] entry_SYSCALL64_slow_path+0x25/0x25 Additional fallout: BTRFS: assertion failed: num_extents, file: fs/btrfs/extent-tree.c, line: 5584 [ cut here ] kernel BUG at fs/btrfs/ctree.h:4320! invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC KASAN CPU: 1 PID: 18815 Comm: trinity-c13 Tainted: GW 4.6.0-rc1-think+ #1 task: 88045de10040 ti: 8803afa38000 task.ti: 8803afa38000 RIP: 0010:[] [] assfail.constprop.88+0x2b/0x2d [btrfs] RSP: 0018:8803afa3f838 EFLAGS: 00010282 RAX: 004e RBX: c046e200 RCX: RDX: RSI: 0003 RDI: ed0075f47efb RBP: 8803afa3f848 R08: 0001 R09: 0001 R10: R11: 0001 R12: 15d0 R13: 8803fda0e048 R14: 8803fda0dc38 R15: 8803fda0dc58 FS: 7fa0566d6700() GS:880468a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa0566d9000 CR3: 000333bc4000 CR4: 001406e0 DR0: 7fa0554fb000 DR1: DR2: DR3: DR6: 0ff0 DR7: 0600 Stack: 8803fda0e048 8803afa3f880 c032288b 880460bb33f8 8803fda0e048 8803fda0dc38 8803fda0dc58 8803afa3f8c8 c032f851 0001 Call Trace: [] drop_outstanding_extent+0x10b/0x130 [btrfs] [] btrfs_delalloc_release_metadata+0x71/0x480 [btrfs] [] ? __btrfs_buffered_write+0xa6f/0xb50 [btrfs] [] btrfs_delalloc_release_space+0x27/0x50 [btrfs] [] __btrfs_buffered_write+0xa28/0xb50 [btrfs] [] ? btrfs_dirty_pages+0x1c0/0x1c0 [btrfs] [] ? filemap_fdatawait_range+0x3e/0x50 [] ? generic_file_direct_write+0x237/0x2f0 [] ? filemap_write_and_wait_range+0xa0/0xa0 [] ? btrfs_file_write_iter+0x670/0x9a0 [btrfs] [] btrfs_file_write_iter+0x74d/0x9a0 [btrfs] [] do_iter_readv_writev+0x153/0x1f0 [] ? btrfs_sync_file+0x920/0x920 [btrfs] [] ? vfs_iter_read+0x1e0/0x1e0 [] ? preempt_count_sub+0xb9/0x130 [] ? percpu_down_read+0x57/0xa0 [] ? __sb_start_write+0xee/0x130 [] ? btrfs_sync_file+0x920/0x920 [btrfs] [] do_readv_writev+0x30f/0x460 [] ? vfs_write+0x2b0/0x2b0 [] ?
Re: btrfs_destroy_inode WARN_ON.
On 2016.03.28 at 10:05 -0400, Josef Bacik wrote: > >Mar 24 10:37:27 x4 kernel: WARNING: CPU: 3 PID: 11838 at > >fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x22b/0x2a0 > > I saw this running some xfstests on our internal kernels but haven't been > able to reproduce it on my latest enospc work (which is obviously perfect). > What were you doing when you tripped this? I'd like to see if I actually > did fix it or if I still need to run it down. Thanks, I cannot really tell. Looking at the backtrace, both Dave and I were running rm. This warning happened just once on my machine, so the issue is obviously very hard to trigger. -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs_destroy_inode WARN_ON.
On 03/25/2016 04:25 AM, Markus Trippelsdorf wrote:
On 2016.03.24 at 18:54 -0400, Dave Jones wrote:
Just hit this on a tree from earlier this morning, v4.5-11140 or so.
WARNING: CPU: 2 PID: 32570 at fs/btrfs/inode.c:9261
btrfs_destroy_inode+0x389/0x3f0 [btrfs]
CPU: 2 PID: 32570 Comm: rm Not tainted 4.5.0-think+ #14
c039baf9 ef721ef0 88025966fc08 8957bcdb
88025966fc50 890b41f1
88045d918040 242d4eed6048 88024eed6048 88024eed6048
Call Trace:
[] ? btrfs_destroy_inode+0x389/0x3f0 [btrfs]
[] dump_stack+0x68/0x9d
[] __warn+0x111/0x130
[] warn_slowpath_null+0x1d/0x20
[] btrfs_destroy_inode+0x389/0x3f0 [btrfs]
[] destroy_inode+0x67/0x90
[] evict+0x1b7/0x240
[] iput+0x3ae/0x4e0
[] ? dput+0x20e/0x460
[] do_unlinkat+0x256/0x440
[] ? do_rmdir+0x350/0x350
[] ? syscall_trace_enter_phase1+0x87/0x260
[] ? enter_from_user_mode+0x50/0x50
[] ? __lock_is_held+0x25/0xd0
[] ? mark_held_locks+0x22/0xc0
[] ? syscall_trace_enter_phase2+0x12d/0x3d0
[] ? SyS_rmdir+0x20/0x20
[] SyS_unlinkat+0x1b/0x30
[] do_syscall_64+0xf4/0x240
[] entry_SYSCALL64_slow_path+0x25/0x25
---[ end trace a48ce4e6a1b5e409 ]---
That's WARN_ON(BTRFS_I(inode)->csum_bytes);
*maybe* it's a bad disk, but there's no indication in dmesg of anything awry.
Spinning rust on SATA, nothing special.
Same thing here:
Mar 24 10:37:27 x4 kernel: [ cut here ]
Mar 24 10:37:27 x4 kernel: WARNING: CPU: 3 PID: 11838 at fs/btrfs/inode.c:9261
btrfs_destroy_inode+0x22b/0x2a0
Mar 24 10:37:27 x4 kernel: CPU: 3 PID: 11838 Comm: rm Not tainted
4.5.0-11787-ga24e3d414e59-dirty #64
Mar 24 10:37:27 x4 kernel: Hardware name: System manufacturer System Product
Name/M4A78T-E, BIOS 350304/13/2011
Mar 24 10:37:27 x4 kernel: 813c0d1a 81b8bb84
812ffd0b
Mar 24 10:37:27 x4 kernel: 81099a9a 880149b86088
88021585f000
Mar 24 10:37:27 x4 kernel: 812ffd0b 88005f526000
Mar 24 10:37:27 x4 kernel: Call Trace:
Mar 24 10:37:27 x4 kernel: [] ? dump_stack+0x46/0x6c
Mar 24 10:37:27 x4 kernel: [] ?
btrfs_destroy_inode+0x22b/0x2a0
Mar 24 10:37:27 x4 kernel: [] ? warn_slowpath_null+0x5a/0xe0
Mar 24 10:37:27 x4 kernel: [] ?
btrfs_destroy_inode+0x22b/0x2a0
Mar 24 10:37:27 x4 kernel: [] ? do_unlinkat+0x13c/0x3e0
Mar 24 10:37:27 x4 kernel: [] ?
entry_SYSCALL_64_fastpath+0x13/0x8f
Mar 24 10:37:27 x4 kernel: ---[ end trace e9bae5be848e7a9e ]---
I saw this running some xfstests on our internal kernels but haven't
been able to reproduce it on my latest enospc work (which is obviously
perfect). What were you doing when you tripped this? I'd like to see
if I actually did fix it or if I still need to run it down. Thanks,
Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs_destroy_inode WARN_ON.
On Thu, Mar 24, 2016 at 06:54:11PM -0400, Dave Jones wrote: > Just hit this on a tree from earlier this morning, v4.5-11140 or so. > > WARNING: CPU: 2 PID: 32570 at fs/btrfs/inode.c:9261 > btrfs_destroy_inode+0x389/0x3f0 [btrfs] > CPU: 2 PID: 32570 Comm: rm Not tainted 4.5.0-think+ #14 > c039baf9 ef721ef0 88025966fc08 8957bcdb > 88025966fc50 890b41f1 > 88045d918040 242d4eed6048 88024eed6048 88024eed6048 > Call Trace: > [] ? btrfs_destroy_inode+0x389/0x3f0 [btrfs] > [] dump_stack+0x68/0x9d > [] __warn+0x111/0x130 > [] warn_slowpath_null+0x1d/0x20 > [] btrfs_destroy_inode+0x389/0x3f0 [btrfs] > [] destroy_inode+0x67/0x90 > [] evict+0x1b7/0x240 > [] iput+0x3ae/0x4e0 > [] ? dput+0x20e/0x460 > [] do_unlinkat+0x256/0x440 > [] ? do_rmdir+0x350/0x350 > [] ? syscall_trace_enter_phase1+0x87/0x260 > [] ? enter_from_user_mode+0x50/0x50 > [] ? __lock_is_held+0x25/0xd0 > [] ? mark_held_locks+0x22/0xc0 > [] ? syscall_trace_enter_phase2+0x12d/0x3d0 > [] ? SyS_rmdir+0x20/0x20 > [] SyS_unlinkat+0x1b/0x30 > [] do_syscall_64+0xf4/0x240 > [] entry_SYSCALL64_slow_path+0x25/0x25 > ---[ end trace a48ce4e6a1b5e409 ]--- > > > That's WARN_ON(BTRFS_I(inode)->csum_bytes); > > *maybe* it's a bad disk, but there's no indication in dmesg of anything awry. > Spinning rust on SATA, nothing special. Same WARN_ON is reachable from umount too.. WARNING: CPU: 2 PID: 20092 at fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x40c/0x480 [btrfs] CPU: 2 PID: 20092 Comm: umount Tainted: GW 4.5.0-think+ #1 a32c482b 8803cd187b60 9d63af84 c05c5e40 c04d316c 8803cd187ba8 9d0c4c27 880460d80040 242dcd187bb0 Call Trace: [] dump_stack+0x95/0xe1 [] ? btrfs_destroy_inode+0x40c/0x480 [btrfs] [] __warn+0x147/0x170 [] warn_slowpath_null+0x31/0x40 [] btrfs_destroy_inode+0x40c/0x480 [btrfs] [] ? btrfs_test_destroy_inode+0x40/0x40 [btrfs] [] destroy_inode+0x77/0xb0 [] evict+0x20e/0x2c0 [] dispose_list+0x70/0xb0 [] evict_inodes+0x26f/0x2c0 [] ? inode_add_lru+0x60/0x60 [] ? fsnotify_unmount_inodes+0x215/0x2c0 [] generic_shutdown_super+0x76/0x1c0 [] kill_anon_super+0x29/0x40 [] btrfs_kill_super+0x31/0x130 [btrfs] [] deactivate_locked_super+0x6f/0xb0 [] deactivate_super+0x99/0xb0 [] cleanup_mnt+0x70/0xd0 [] __cleanup_mnt+0x1b/0x20 [] task_work_run+0xef/0x130 [] exit_to_usermode_loop+0xf9/0x100 [] do_syscall_64+0x238/0x2b0 [] entry_SYSCALL64_slow_path+0x25/0x25 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs_destroy_inode WARN_ON.
On 2016.03.24 at 18:54 -0400, Dave Jones wrote: > Just hit this on a tree from earlier this morning, v4.5-11140 or so. > > WARNING: CPU: 2 PID: 32570 at fs/btrfs/inode.c:9261 > btrfs_destroy_inode+0x389/0x3f0 [btrfs] > CPU: 2 PID: 32570 Comm: rm Not tainted 4.5.0-think+ #14 > c039baf9 ef721ef0 88025966fc08 8957bcdb > 88025966fc50 890b41f1 > 88045d918040 242d4eed6048 88024eed6048 88024eed6048 > Call Trace: > [] ? btrfs_destroy_inode+0x389/0x3f0 [btrfs] > [] dump_stack+0x68/0x9d > [] __warn+0x111/0x130 > [] warn_slowpath_null+0x1d/0x20 > [] btrfs_destroy_inode+0x389/0x3f0 [btrfs] > [] destroy_inode+0x67/0x90 > [] evict+0x1b7/0x240 > [] iput+0x3ae/0x4e0 > [] ? dput+0x20e/0x460 > [] do_unlinkat+0x256/0x440 > [] ? do_rmdir+0x350/0x350 > [] ? syscall_trace_enter_phase1+0x87/0x260 > [] ? enter_from_user_mode+0x50/0x50 > [] ? __lock_is_held+0x25/0xd0 > [] ? mark_held_locks+0x22/0xc0 > [] ? syscall_trace_enter_phase2+0x12d/0x3d0 > [] ? SyS_rmdir+0x20/0x20 > [] SyS_unlinkat+0x1b/0x30 > [] do_syscall_64+0xf4/0x240 > [] entry_SYSCALL64_slow_path+0x25/0x25 > ---[ end trace a48ce4e6a1b5e409 ]--- > > > That's WARN_ON(BTRFS_I(inode)->csum_bytes); > > *maybe* it's a bad disk, but there's no indication in dmesg of anything awry. > Spinning rust on SATA, nothing special. Same thing here: Mar 24 10:37:27 x4 kernel: [ cut here ] Mar 24 10:37:27 x4 kernel: WARNING: CPU: 3 PID: 11838 at fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x22b/0x2a0 Mar 24 10:37:27 x4 kernel: CPU: 3 PID: 11838 Comm: rm Not tainted 4.5.0-11787-ga24e3d414e59-dirty #64 Mar 24 10:37:27 x4 kernel: Hardware name: System manufacturer System Product Name/M4A78T-E, BIOS 350304/13/2011 Mar 24 10:37:27 x4 kernel: 813c0d1a 81b8bb84 812ffd0b Mar 24 10:37:27 x4 kernel: 81099a9a 880149b86088 88021585f000 Mar 24 10:37:27 x4 kernel: 812ffd0b 88005f526000 Mar 24 10:37:27 x4 kernel: Call Trace: Mar 24 10:37:27 x4 kernel: [] ? dump_stack+0x46/0x6c Mar 24 10:37:27 x4 kernel: [] ? btrfs_destroy_inode+0x22b/0x2a0 Mar 24 10:37:27 x4 kernel: [] ? warn_slowpath_null+0x5a/0xe0 Mar 24 10:37:27 x4 kernel: [] ? btrfs_destroy_inode+0x22b/0x2a0 Mar 24 10:37:27 x4 kernel: [] ? do_unlinkat+0x13c/0x3e0 Mar 24 10:37:27 x4 kernel: [] ? entry_SYSCALL_64_fastpath+0x13/0x8f Mar 24 10:37:27 x4 kernel: ---[ end trace e9bae5be848e7a9e ]--- -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
btrfs_destroy_inode WARN_ON.
Just hit this on a tree from earlier this morning, v4.5-11140 or so. WARNING: CPU: 2 PID: 32570 at fs/btrfs/inode.c:9261 btrfs_destroy_inode+0x389/0x3f0 [btrfs] CPU: 2 PID: 32570 Comm: rm Not tainted 4.5.0-think+ #14 c039baf9 ef721ef0 88025966fc08 8957bcdb 88025966fc50 890b41f1 88045d918040 242d4eed6048 88024eed6048 88024eed6048 Call Trace: [] ? btrfs_destroy_inode+0x389/0x3f0 [btrfs] [] dump_stack+0x68/0x9d [] __warn+0x111/0x130 [] warn_slowpath_null+0x1d/0x20 [] btrfs_destroy_inode+0x389/0x3f0 [btrfs] [] destroy_inode+0x67/0x90 [] evict+0x1b7/0x240 [] iput+0x3ae/0x4e0 [] ? dput+0x20e/0x460 [] do_unlinkat+0x256/0x440 [] ? do_rmdir+0x350/0x350 [] ? syscall_trace_enter_phase1+0x87/0x260 [] ? enter_from_user_mode+0x50/0x50 [] ? __lock_is_held+0x25/0xd0 [] ? mark_held_locks+0x22/0xc0 [] ? syscall_trace_enter_phase2+0x12d/0x3d0 [] ? SyS_rmdir+0x20/0x20 [] SyS_unlinkat+0x1b/0x30 [] do_syscall_64+0xf4/0x240 [] entry_SYSCALL64_slow_path+0x25/0x25 ---[ end trace a48ce4e6a1b5e409 ]--- That's WARN_ON(BTRFS_I(inode)->csum_bytes); *maybe* it's a bad disk, but there's no indication in dmesg of anything awry. Spinning rust on SATA, nothing special. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
