Weird behaviour with lsblk and freshly created loop device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Right after associating a loop device with a disk image file, I'm using
lsblk to retrieve some info about the partitions.

If I'm doing this as root:

  $ losetup /dev/loop0 /tmp/installer-disks/disk0.img && lsblk -n --raw
--paths -o NAME,PARTTYPE /dev/loop0 && losetup -d /dev/loop0

then the output is missing the parttypes:

  /dev/loop0
  /dev/loop0p1
  /dev/loop0p2

However adding a sleep or 'udevadm settle' after setting the loop device
the parttypes are correctly showed:

   $ losetup /dev/loop0 /tmp/installer-disks/disk0.img && udevadm settle
&& lsblk -n --raw --paths -o NAME,PARTTYPE /dev/loop0 && losetup -d
/dev/loop0
  /dev/loop0
  /dev/loop0p1 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f
  /dev/loop0p2 4f68bce3-e8cd-4db1-96e7-fbcaf984b709

Could anybody tell me if that's expected ?

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux