Looks like I found an unrelated bug, though, that messed with my testing. And it looks like a nasty one: once "btrfs dev scan" sees a disk, it stores its device and will then happily use it without verification even if it's been pulled out and replaced by something else. Lemme investigate that later today.
A missing device scanned after the FS mount - would just appear as being used by the FS tree, but actually its not. BTRFS does not handle the online reappear of the device that is the device which is not found at the mount/open-ctree won't be part of the alloc_dev_list, yet. HTH Anand
It would be nice if you can send detailed info to mail list. AFAIK, btrfs will check its superblock for devid and device UUID, to ensure that's the device we're using.
-- 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
