search for: uuid_sub

Hallo, linux-btrfs, please delete the option "-L" (for labelling) in "mkfs.btrfs", in some configurations it doesn''t work as expected. My usual way: mkfs.btrfs -d raid0 -m raid1 /dev/sdb /dev/sdc /dev/sdd ... One call for some devices. Wenn I add the option "-L mylabel" then each device gets the same label, and therefore some other programs

...4456807582104f8ab12eb6411a80b31a > root=UUID=1b0d6168-50f1-4ceb-b6ac-85e55206e2d4 ro crashkernel=auto > rd.md.uuid=ea5fede7:dc339c3b:81817fc4:aba0bd89 > rd.md.uuid=7a90faed:4e5a2b50:9baa8249:21a6c3da rhgb quiet > /dev/sda1: UUID="6f900f10-d951-2ae7-712c-a5710d8d7316" > UUID_SUB="541c8849-58bd-8309-96fd-b45faf0d40bb" LABEL="localhost:home" > TYPE="linux_raid_member" > /dev/sda2: UUID="ea5fede7-dc33-9c3b-8181-7fc4aba0bd89" > UUID_SUB="f127cce4-82f6-fa86-6bc5-2c6b8e3f8e7a" LABEL="localhost:root" > TYP...

...ot;ca924fad-..." TYPE="ext4" /dev/mapper/vg_internal_e-lv_internal_srv: UUID="f85b7a2c-..." TYPE="crypto_LUKS" vg_internal_e /dev/md3: UUID="1Fi2Ex-..." TYPE="LVM2_member" /dev/sda4: UUID="00029bd4-..." UUID_SUB="d0024074-..." LABEL="e.ld:3" TYPE="linux_raid_member" /dev/sdb4: UUID="00029bd4-..." UUID_SUB="bf98fc79-..." LABEL="e.ld:3" TYPE="linux_raid_member" beside blkid any other tool available? -- Thanks, LF

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and

Hi, This left me puzzled for a while: 22:29 borg:/ # losetup /dev/loop1 /.B.disk 22:29 borg:/ # mount /dev/loop1 /B mount: /dev/loop1: can''t read superblock 22:29 borg:/ # blkid /dev/loop1 /dev/loop1: UUID="e19fe89b-cde3-4ccc-bc70-b759a57bd1c9" UUID_SUB="f29c6218-d040-4546-a227-4dd2d2142817" TYPE="btrfs" 22:29 borg:/ # losetup -d /dev/loop1 22:29 borg:/ # losetup /dev/loop2 /.B.disk 22:29 borg:/ # mount /dev/loop2 /B (success) So the btrfs volume is tied to loop2? That certainly is not good. Even real disks (/dev/sd*) can mo...

...PE="ext4" > /dev/mapper/vg_internal_e-lv_internal_srv: UUID="f85b7a2c-..." TYPE="crypto_LUKS" > vg_internal_e > /dev/md3: UUID="1Fi2Ex-..." TYPE="LVM2_member" > /dev/sda4: UUID="00029bd4-..." UUID_SUB="d0024074-..." LABEL="e.ld:3" TYPE="linux_raid_member" > /dev/sdb4: UUID="00029bd4-..." UUID_SUB="bf98fc79-..." LABEL="e.ld:3" TYPE="linux_raid_member" > > beside blkid any other tool available? > > --...

...;device>'. The following +fields are usually present in the returned hash. Other fields may also be present. + +C<device> should be a block device or patition, for example C</dev/sda> or C</dev/sdb1>. + +=over + +=item C<UUID> + +The uuid of this device. + +=item C<UUID_SUB> + +The sub uuid of this device. + +=item C<LABEL> + +The label of this device. + +=item C<VERSION> + +The version of blkid command. + +=item C<TYPE> + +The filesystem type or RAID of this device. + +=item C<USAGE> + +The usage of this device, for example C<filesystem&...

Hi, I''ve some btrfs fs which are encrypted with loopaes. I decrypt them in a script during bootup. Now I want to determine if the decrypted fs is a btrfs fs. If not I missspelled the password and I can handle that error in my script. Thanks for any help! Felix -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to