Hello folks, I reported a bug here: https://bugzilla.kernel.org/show_bug.cgi?id=63071 but I am not sure if that was the right thing to do. This is producing OOM issues and leading to system crashes (including eventual panics) with such alarming frequency that I wonder if perhaps there is something different about my setup than others. In a nutshell, I originally made the mistake of storing a VirtualBox 40G .vdi file on a btrfs partition (kernel 3.10). I managed to copy it to a file marked chattr +C (I read the wiki *NOW*), but I couldn't delete the original file -- rm hangs the system. (I actually have the original file and another made with cp --reflink of it, while trying to diagnose the issue. I need to rm both of them) rm starts out with lots of hard disk activity, then that stops. I eventually get the attached kernel BUG, then a little bit later it panics due to out of memory. But later I had the virtually identical problem on another system, this one on just a 5GB file with about 25,000 extents (it was the restoresymtable from restore(8) from the e2fs dump/restore pair). That took down my server, trying to delete it. I would have expected btrfs to be more resilient by this point. Any ideas? Thanks, John -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
