So far, debugging suggests that the event processing themselves is causing the inotify change event. Disabling any processing for the change event stops the events.
(ie. they don't show up in normal disk activity - thus udev is responding to itself. With our custom LVM and mdadm rules, this probably explains why it doesn't show up upstream either) ** Summary changed: - [jaunty] doesn't boot anymore after udev upgrade + udev repeatedly generates "change" events for the same block device(s) -- udev repeatedly generates "change" events for the same block device(s) https://bugs.launchpad.net/bugs/332270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
