On Sun, Mar 01, 2015 at 10:27:49AM +0200, Boaz Harrosh wrote: > On 02/27/2015 02:58 AM, Dave Chinner wrote: > >> It looks like the system anticipates that ramdisk "should > >> not have these events" > > > > Right, but not because it's a ramdisk. Those events should not be > > occurring because I'm not creating or destroying devices, I'm not > > changing partition tables, I'm not resizing ramdisks or partitions, > > and so on. I'm simply mkfs'ing, mounting and unmounting filesystems > > on the ramdisks - nothing should be generating device based udev > > events... > > > > Finding the trigger that is causing these events will tell us what > > the bug is - > > > restricting the config won't help, especially as DAX > > will *always* be enabled on my test machines as it's something > > needed in my test matrix. > > No the "if DAX" is for the 4k thing. The enablement of the uevents is > with a new "part_show" module parameter (See patch-1). Sure, but that doesn't answer my question: what is generating device level uevents when all I'm doing is mkfs/mount/umount on the device? > > I'm not sure how to go about finding that > > trigger right now and as such I won't really have time to look at it > > until after lsfmm/vault... > > > > I'll try to reproduce this here. What Fedora version do I need? I'm running debian unstable w/ systemd-215 on the particular test machine that is hitting this problem. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
