[udev] no uevent when block devices change
Bug #1466081 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Debian) |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Since July 7, udisks2 fails its tests: https:/
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-
Upstream bug: https:/
description: | updated |
Changed in systemd (Debian): | |
status: | Unknown → New |
Changed in systemd (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in systemd (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
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) pseudo_ 0/adapter0/ host2/target2: 0:0/2:0: 0:0/block/ sda (block)
UDEV [41.021205] change /devices/
In wily there is no uevent.