As mentioned in the other thread.. we expect user to check the devices before / after mount and wipefs the disks which should not belong to the fsid.
my bad. I just realized that unmount and wipefs may not be an viable choice in case of btrfs as root fs.
For the case you mentioned, I think the behavior is OK, always use the device with *current* largest generation is a acceptable strategy, since the only things we can depend on the devices we *current* see...
Yeah. let me do that approach as well to take care of picking the correct disk when FS is _unmounted_. And, when FS is mounted we should NOT kick out device paths invariably. which means we still need the patch. Btrfs: device_list_add() should not update list when mounted Thanks, Anand -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
