On Sun, May 29, 2016 at 8:03 PM, Chris Murphy <li...@colorremedies.com> wrote:
> > # lsblk -o +UUID > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID > loop0 7:0 0 10G 0 loop /mnt/0 > 63288b0c-9216-4f11-aed4-cc054ae90e07 > loop1 7:1 0 10G 0 loop > 63288b0c-9216-4f11-aed4-cc054ae90e07 > > This is worse. > > # btrfs fi show > Label: none uuid: 63288b0c-9216-4f11-aed4-cc054ae90e07 > Total devices 2 FS bytes used 384.00KiB > devid 1 size 10.00GiB used 2.02GiB path /dev/loop0 > devid 2 size 10.00GiB used 0.00B path /dev/loop1 > > So is this. Where is the new UUID for the newly created sprout volume? > > /dev/loop0: UUID="63288b0c-9216-4f11-aed4-cc054ae90e07" > UUID_SUB="e379aedb-6d14-4d56-be7d-1772c9984bc5" TYPE="btrfs" > /dev/loop1: UUID="63288b0c-9216-4f11-aed4-cc054ae90e07" > UUID_SUB="b282f566-8382-468e-b9ec-f748244b703b" TYPE="btrfs" > > Uhh? Identical UUIDs for seed and sproud? That's not right. Just to confirm that UUID for the sprout is the same as the seed at mkfs time, and I didn't include it in the previous email: # mkfs.btrfs /dev/loop0 btrfs-progs v4.5.2 See http://btrfs.wiki.kernel.org for more information. Performing full device TRIM (10.00GiB) ... Label: (null) UUID: 63288b0c-9216-4f11-aed4-cc054ae90e07 -- 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
