On Tue, Nov 25, 2014 at 7:11 PM, Zygo Blaxell <zblax...@furryterror.org> wrote: > On Tue, Nov 25, 2014 at 03:46:32PM -0700, Chris Murphy wrote: >> What happens when all btrfs LVs are unmounted, and you lvchange -an >> the LVs (the pair) you do not want mounted; and then btrfs dev scan; >> and then mount one of the devices? It should only find the matching LV >> because the others are deactivated. I know this isn't ideal, but it's >> better than corruption. > > This is one of two possible ways to assemble the btrfs correctly. > The other is to explicitly name all of the devices when mounting.
OK I didn't realize it was possible to explicitly name all of them, the last time I'd tried this (about 9 epochs ago) mount didn't understand being passed two devices before the mount point. > > The challenge for the poor end-user (or inexperienced sysadmin) is to > defeat all the defaults in system installers, initramfs-tools, lvm2, > udev, etc. to prevent btrfs from destroying a filesystem accidentally. I agree if it finds two identical volumes it should fail to mount with some coherent error. -- Chris Murphy -- 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
