> [ ... ] However, the disappearance of the device doesn't get > propagated up to the filesystem correctly, Indeed, sometimes it does, sometimes it does not, in part because of chipset bugs, in part because the USB protocol signaling side does not handle errors well even if the chipset were bug free. > and that is what causes the biggest issue with BTRFS. Because > BTRFS just knows writes are suddenly failing for some reason, > it doesn't try to release the device so that things get > properly cleaned up in the kernel, and thus when the same > device reappears (as it will when the disconnect was due to a > transient bus error, which happens a lot), it shows up as a > different device node, which gets scanned for filesystems by > udev, and BTRFS then gets really confused because it now sees > 3 (or more) devices for a 2 device filesystem. That's a good description that should be on the wiki. -- 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
