This is a known issue in upstream; it appears to hurt usb devices more than sata.
The btrfs module doesn't release the inode properly when the device disappears (you should see the device is still in /dev). When the next transaction commit occurs (in this case, due to a presumably automated umount call), writing out the superblock fails, which triggers the sanity check (the reasoning being that it's much better to noisily and visibly die than to silently corrupt data). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741643 Title: kernel BUG at /build/buildd/linux-2.6.38/fs/btrfs/disk-io.c:2349! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/741643/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
