https://bugzilla.novell.com/show_bug.cgi?id=761788 https://bugzilla.novell.com/show_bug.cgi?id=761788#c Martin Walter changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |dsterba@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761788 https://bugzilla.novell.com/show_bug.cgi?id=761788#c2 --- Comment #2 from David Sterba 2012-05-11 12:58:13 CEST --- That's probably because the system was not in the same state to reproduce it. Snapshotting works, there must be something else triggering the crash. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761788 https://bugzilla.novell.com/show_bug.cgi?id=761788#c4 --- Comment #4 from David Sterba 2012-05-12 01:49:03 CEST --- Did you see any btrfs related messages before the oops traces? Similar to: btrfs unable to find ref byte nr 2054466859008 parent 2054465597440 root 0 owner 0 offset 0 or parent transid verify failed on 2054466859008 wanted 15349 found 175224 During a long snapshot deletion I saw this trace, mostly matches the one you reported, but I see only a warning (and a different kernel from sle11 sp2, but it's very close to the 3.1 based in opensuse): [11642.248223] ------------[ cut here ]------------ [11642.248278] WARNING: at fs/btrfs/extent-tree.c:5040 __btrfs_free_extent+0x6a7/0x7a0 [btrfs]() [11642.248531] Pid: 4712, comm: btrfs-cleaner Tainted: G N 3.0.30-default+ #35 [11642.248538] Call Trace: [11642.248566] [<ffffffff810048b5>] dump_trace+0x75/0x300 [11642.248584] [<ffffffff8144062f>] dump_stack+0x69/0x6f [11642.248600] [<ffffffff81059f3b>] warn_slowpath_common+0x7b/0xc0 [11642.248637] [<ffffffffa0565ef7>] __btrfs_free_extent+0x6a7/0x7a0 [btrfs] [11642.248724] [<ffffffffa0566133>] run_delayed_tree_ref+0x143/0x150 [btrfs] [11642.248798] [<ffffffffa056643e>] run_clustered_refs+0xce/0x320 [btrfs] [11642.248871] [<ffffffffa05667c9>] btrfs_run_delayed_refs+0x139/0x2e0 [btrfs] [11642.248948] [<ffffffffa0576484>] btrfs_commit_transaction+0xd4/0x8f0 [btrfs] [11642.249040] [<ffffffffa0568c1c>] btrfs_drop_snapshot+0x25c/0x650 [btrfs] [11642.249115] [<ffffffffa0574e2b>] btrfs_clean_one_old_snapshot+0x12b/0x160 [btrfs] [11642.249205] [<ffffffffa05709f4>] cleaner_kthread+0x154/0x1e0 [btrfs] [11642.249266] [<ffffffff8107b7b6>] kthread+0x96/0xa0 [11642.249278] [<ffffffff8144c544>] kernel_thread_helper+0x4/0x10 [11642.249287] ---[ end trace afeaa46b2c33a468 ]--- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761788 https://bugzilla.novell.com/show_bug.cgi?id=761788#c6 --- Comment #6 from Martin Walter 2012-05-12 12:12:08 UTC --- Created an attachment (id=490599) --> (http://bugzilla.novell.com/attachment.cgi?id=490599) dmesg after snapshot the rootfs on supermicro with 3.1.10-37 Too bad! Just upgraded my second test-machine (supermicro) to 3.1.10-37 and was glad to find zfs also supported. Then I took a snaphot of the root-fs and got again our kernel-bug! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=761788 https://bugzilla.novell.com/show_bug.cgi?id=761788#c8 David Sterba changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #8 from David Sterba 2013-11-25 17:22:20 CET --- Never reproduced here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.