FS#56112 - No Disk-Label or UUID under /dev/disk/ if you use mkfs.btrfs
Attached to Project:
Release Engineering
Opened by Nicolai Mladenoff (unicks) - Wednesday, 25 October 2017, 12:25 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 28 October 2017, 17:17 GMT
Opened by Nicolai Mladenoff (unicks) - Wednesday, 25 October 2017, 12:25 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 28 October 2017, 17:17 GMT
|
Details
Description:
If you make a Btrfs (BTree-filesystem) with "mkfs.btrfs -L ROOT /dev/sda2", there is no label or UUID under /dev/disk created. (This is not the case, if you use e.g. "mkfs.ext4 -L BOOT /dev/sda1"). Now "genfstab -Lp /mnt >> /mnt/etc/fstab" uses device name "/dev/sda2" instead of "LABEL=ROOT". After installation and first boot, labels and uuid exits under /dev/disk as expected. Steps to reproduce: Boot Arch ISO from Oktober 1st and create a Btrfs (BTree-filesystem) with "mkfs.btrfs -L ROOT /dev/sda2", then look at /dev/disk/by-id or /dev/disk/by-uuid no label or uuid for the Btrfs. But "blkid /dev/sda2" will show Label and UUID. My partition layout MS_DOS: /dev/sda1 - EXT4 LABEL=BOOT /dev/sda2 - Btrfs LABEL=ROOT /dev/sda3 - swap LABEL=SWAP or GPT UEFI: /dev/sda1 - fat32 ESP LABEL=EFI /dev/sda2 - Btrfs LABEL=ROOT /dev/sda3 - swap LABEL=SWAP |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Saturday, 28 October 2017, 17:17 GMT
Reason for closing: Not a bug
Additional comments about closing: Not archiso issue.
Saturday, 28 October 2017, 17:17 GMT
Reason for closing: Not a bug
Additional comments about closing: Not archiso issue.
If you run 'udevadm monitor' while you run mkfs.btrfs, do you see uevents for the relevant block device of both KERNEL and UDEV variety? What does 'udevadm info /dev/...' show before and after mkfs?
Maybe a Virtualbox Bug?
Host system is Arch Linx, Kernel 4.13.8-1-ARCH, Virtualbox 5.2.0-1.
I had the same problem with the Antergos IOS (screenshot), then I tried Arch ISO and same thing. Not sure what changed?
This time I had udevadm monitor on tty2.
Then on /dev/sda2 with LABEL=B it worked as expected. Very strange?
Screenshots attached.