As a data point, I noticed that e2fsck was upgraded last night, so I touched '/forcefsck'. This resulted in mountall outputing:
trigger_events: local 5/5 remote 0/0 virtual 11/11 swap 1/1
(eventually)
So, it really does seem like things are timing related. I have a 155Mb strace output (since it followed the e2fsck processes) in case that is useful -- but I will note that it appears that the filesystem event was still not triggered.
As a data point, I noticed that e2fsck was upgraded last night, so I touched '/forcefsck'. This resulted in mountall outputing:
trigger_events: local 5/5 remote 0/0 virtual 11/11 swap 1/1
(eventually)
So, it really does seem like things are timing related. I have a 155Mb strace output (since it followed the e2fsck processes) in case that is useful -- but I will note that it appears that the filesystem event was still not triggered.