<div dir="ltr">It looks like your system has:<br><ol><li>Kernel crash dump configured.</li><li>Something is causing crash while you issue a reboot, may be some module unload path has a bug.<br></li><li>Crash is triggering kernel dump to take dump of memory (I guess you have plenty of RAM to justify 45 minutes) in /var/core directory. Although dump image is highly compressible but compression is the last step.<br>
</li><li>If there is no space in /var/core, kdump gives up and you see faster reboot.</li></ol><p>-Rajat<br></p></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 12:39 PM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Fri, 30 May 2014 12:32:32 -0700, Vipul Jain said:<br>
<br>
> On my system I have /var/core directory created which has 300G space and if<br>
> I fill the /var/core with files say upto 290G and reboot the system and<br>
> after it comes up and delete the files in /var/core and try to reboot the<br>
> system takes 45 mins before it actually reboots. Wondering if anyone has<br>
> seen this before and what could be the issue?<br>
<br>
</div>Is this reproducible?<br>
<br>
Do you have any clue at all where in the reboot process it's sitting<br>
for the 45 minutes?<br>
<br>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><br></div>