On Mon, Jan 23, 2017 at 08:51:24PM -0700, Chris Murphy wrote: > On Mon, Jan 23, 2017 at 5:05 PM, Omar Sandoval <osandov@xxxxxxxxxxx> wrote: > > Thanks! Hmm, okay, so it's coming from btrfs_update_delayed_inode()... > > That's probably us failing btrfs_lookup_inode(), but just to make sure, > > could you apply the updated diff at the same link as before > > (https://gist.github.com/osandov/9f223bda27f3e1cd1ab9c1bd634c51a4)? If > > that's the case, I'm even more confused about what xattrs have to do > > with it. > > [ 35.015363] __btrfs_update_delayed_inode(): inode is missing Okay, like I expected... > [ 35.015372] btrfs_update_delayed_inode(ino=2) -> -2 Wtf? Inode numbers should be >=256. I updated the diff a third time to catch where that came from. If we're lucky, the backtrace should have the exact culprit. If we're unlucky, there might be memory corruption involved. > osandov-9f223b_2-dmesg.log > https://drive.google.com/open?id=0B_2Asp8DGjJ9UnNSRXpualprWHM > > > -- > Chris Murphy -- 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
