Re: waiting for an unknown set of udev /dev entries to complete

[Patrick Mansfield <patmans@us.ibm.com>]

On Fri, Nov 18, 2005 at 02:30:45PM -0800, Patrick Mansfield wrote:

> With current FC rawhide/devel, I am working on iscsi install, and had udev
> "error" logging enabled on a medium speed dual processor system. So the
> scripts are very slow, and the partition setup code is being run right
> after iscsi scan (really discovery/login and then scan) and it does not
> see all the devices (and I probably have some bugs still). 

It ends up that it is the iSCSI scan is running very slowly, and that the
current open-iscsi returns if the scan takes more than 3 seconds (and also
leaves an unreaped iscsid process each time).

So, it was not that udev was slow here, it was that the iscsi login/scan
returned before the scan was even *complete*, so of course there were
still udev events in progress after the iscsadm login returned.

It took a while to notice since I had udev info (not error ...) logging
on, and missed the intermixed scsi discovery output. Plus, iscsid didn't
log any errors.

-- Patrick Mansfield


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel