http://bugzilla.novell.com/show_bug.cgi?id=557609 http://bugzilla.novell.com/show_bug.cgi?id=557609#c1 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |NEEDINFO CC| |matz@novell.com Info Provider| |alext@novell.com --- Comment #1 from Stephan Kulow 2009-12-08 13:29:13 UTC --- what is in your prepared file? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557609 http://bugzilla.novell.com/show_bug.cgi?id=557609#c3 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alext@novell.com --- Comment #3 from Stephan Kulow 2010-01-21 16:06:51 UTC --- you have a lot of files referenced in there and it tries to read them all - so it's not suprising it takes a while. 8 minutes is a bit much though. Can you strace preload to see what it works on? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557609 http://bugzilla.novell.com/show_bug.cgi?id=557609#c5 --- Comment #5 from Alex Tsariounov 2010-02-27 18:15:41 UTC --- Sorry, but I've not had time to debug the issue yet. I get around it by putting "nopreload" into /etc/sysconfig/bootloader for the kernel boot options. I don't notice any degradation from not preloading, but did notice degradation when preloading was active. I'll do an strace soon. One thing to note is that I never intentionally added files to the prepared file (don't even know how to do that). The preload file was generated for me by install and day to day operation. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557609 http://bugzilla.novell.com/show_bug.cgi?id=557609#c7 Vladimir Psenicka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|alext@novell.com | --- Comment #7 from Vladimir Psenicka 2010-03-27 10:12:12 UTC --- Created an attachment (id=350987) --> (http://bugzilla.novell.com/attachment.cgi?id=350987) preload strace log After slow preload (about 10 minutes) I restarted PC and straced preload process, but this time preload ended quick (about 2 minutes) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557609 http://bugzilla.novell.com/show_bug.cgi?id=557609#c9 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|matz@novell.com | --- Comment #9 from Michael Matz 2010-06-25 12:05:33 UTC --- The values in comment #7 strace log are completely bollocks. Repeated fadvices on files 10,11,12,13,17 with sizes and offsets being nonsensical: E.g.: 370 1269684166.071359 fadvise64(13, 3422535680, 8388608, POSIX_FADV_WILLNEED) 370 1269684166.290542 fadvise64(12, 1653669888, 7274496, POSIX_FADV_WILLNEED) So, file 13 at offset 3.4 GB, reading 8MB in size. And so on ... Unfortunately the strace doesn't show us which files are connected with those file descriptors. But files of such size can't possibly be interesting files to preload. Such files normally shouldn't be involved in the startup process at all. One guess would be for instance some log file gone wild, that the preload tracer sees as being opened and hence like to read in completely. Instead of introducing an artificial limit on filesize (size > N --> don't preload at all), or on read data size (ala always read in N MB max, per file), I'd first like to know which files are the ones being so large. But as stop-gap measure, I do think it makes sense to not preload, say, 8 MB per file (or to ignore all files > say 16 MB, this needs to be a bit large so as to not ignore some of the very large shared libraries we have). One other idea: if the above files are indeed logfiles or the like, then they are probably opened O_WRONLY. We can map such open calls to just being stat()s, instead of causing a full read-in. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=557609 https://bugzilla.novell.com/show_bug.cgi?id=557609#c11 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #11 from Stephan Kulow 2011-09-01 13:42:37 CEST --- I dropped preload for 12.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.