desktop-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

This is because in wily, fs operations like mkfs, e2label, or other
things which directly open the block device don't trigger a change event
any more:

 $ sudo modprobe scsi_debug
 $ udevadm monitor

Then run this in another terminal: sudo sh -c '> /dev/sda'

Up to vivid you get

KERNEL[40.913525] change   /devices/pseudo_0/adapter0/host2/target2:0:0/2:0:0:0/block/sda (block)
UDEV  [41.021205] change   /devices/pseudo_0/adapter0/host2/target2:0:0/2:0:0:0/block/sda (block)

In wily there is no uevent.

** Summary changed:

- Does not update properties any more when file systems change
+ no uevent when block devices change

** Changed in: udisks2 (Ubuntu)
       Status: New => Incomplete

** Changed in: udisks2 (Ubuntu)
       Status: Incomplete => Triaged

** Changed in: udisks2 (Ubuntu)
   Importance: Undecided => High

** Tags added: regression-release

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1466081

Title:
  no uevent when block devices change

Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  Since July 7, udisks2 fails its tests:
  https://jenkins.qa.ubuntu.com/job/wily-adt-udisks2/

  After a file system operation like mkfs or e2label udisks2 does not
  update its properties any more. This can be replicated easily locally
  with e. g.

    sudo modprobe scsi_debug
    sudo mkfs.ext2 -L old /dev/sda
    udisksctl info -b /dev/sdb
    # -> no IdType, IdLabel, etc.

  It starts being correct after manually triggering an uevent with "sudo
  udevadm trigger -v --sysname-match=sdb".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1466081/+subscriptions