Linux reboot command takes too long
Hi All, I have a quick question on Linux reboot: On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue? Regards, Vipul.
On Fri, 30 May 2014 12:32:32 -0700, Vipul Jain said:
On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue?
Is this reproducible? Do you have any clue at all where in the reboot process it's sitting for the 45 minutes?
It looks like your system has: 1. Kernel crash dump configured. 2. Something is causing crash while you issue a reboot, may be some module unload path has a bug. 3. 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. 4. If there is no space in /var/core, kdump gives up and you see faster reboot. -Rajat On Fri, May 30, 2014 at 12:39 PM, <Valdis.Kletnieks@vt.edu> wrote:
On Fri, 30 May 2014 12:32:32 -0700, Vipul Jain said:
On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue?
Is this reproducible?
Do you have any clue at all where in the reboot process it's sitting for the 45 minutes?
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Fri, May 30, 2014 at 12:32 PM, Vipul Jain <vipulsj@gmail.com> wrote:
Hi All,
I have a quick question on Linux reboot: On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue?
Regards, Vipul.
Anybody knowns what does below means: ps elxf | grep shutdown 4 0 6327 3842 20 0 12496 788 jbd2_l D ? 0:00 \_ shutdown -r 0 wCONSOLE=/dev/console TERM=linux SHELL=/bin/sh rootmnt=/root cpiorootsize= crashkernel=512M@128M image=/xxx/image1/ INIT_VERSION=sysvinit-2.88 init=/sbin/init COLUMNS=80 PATH=/xxx/sbin:/xxx/bin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=2 RUNLEVEL=2 PWD=/root PREVLEVEL=N previous=N LINES=24 HOME=/ SHLVL=2 env=0x3DA97000 _=/sbin/shutdown 0 0 6764 6651 20 0 6304 600 pipe_w S+ pts/0 0:00 \_ grep shutdownTERM=xterm SHELL=/bin/bash SSH_CLIENT=172.16.92.39 49891 22 SSH_TTY=/dev/pts/0 USER=root MAIL=/var/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PWD=/root SHLVL=1 HOME=/root LOGNAME=root SSH_CONNECTION=172.16.92.39 49891 172.16.85.88 22 _=/bin/grep
you have kdump enabled crashkernel=512M@128M On Fri, May 30, 2014 at 2:38 PM, Vipul Jain <vipulsj@gmail.com> wrote:
On Fri, May 30, 2014 at 12:32 PM, Vipul Jain <vipulsj@gmail.com> wrote:
Hi All,
I have a quick question on Linux reboot: On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue?
Regards, Vipul.
Anybody knowns what does below means: ps elxf | grep shutdown 4 0 6327 3842 20 0 12496 788 jbd2_l D ? 0:00 \_ shutdown -r 0 wCONSOLE=/dev/console TERM=linux SHELL=/bin/sh rootmnt=/root cpiorootsize= crashkernel=512M@128M image=/xxx/image1/ INIT_VERSION=sysvinit-2.88 init=/sbin/init COLUMNS=80 PATH=/xxx/sbin:/xxx/bin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=2 RUNLEVEL=2 PWD=/root PREVLEVEL=N previous=N LINES=24 HOME=/ SHLVL=2 env=0x3DA97000 _=/sbin/shutdown 0 0 6764 6651 20 0 6304 600 pipe_w S+ pts/0 0:00 \_ grep shutdownTERM=xterm SHELL=/bin/bash SSH_CLIENT=172.16.92.39 49891 22 SSH_TTY=/dev/pts/0 USER=root MAIL=/var/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PWD=/root SHLVL=1 HOME=/root LOGNAME=root SSH_CONNECTION=172.16.92.39 49891 172.16.85.88 22 _=/bin/grep
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Fri, May 30, 2014 at 3:19 PM, Rajat Sharma <fs.rajat@gmail.com> wrote:
you have kdump enabled crashkernel=512M@128M
On Fri, May 30, 2014 at 2:38 PM, Vipul Jain <vipulsj@gmail.com> wrote:
On Fri, May 30, 2014 at 12:32 PM, Vipul Jain <vipulsj@gmail.com> wrote:
Hi All,
I have a quick question on Linux reboot: On my system I have /var/core directory created which has 300G space and if I fill the /var/core with files say upto 290G and reboot the system and after it comes up and delete the files in /var/core and try to reboot the system takes 45 mins before it actually reboots. Wondering if anyone has seen this before and what could be the issue?
Regards, Vipul.
Anybody knowns what does below means: ps elxf | grep shutdown 4 0 6327 3842 20 0 12496 788 jbd2_l D ? 0:00 \_ shutdown -r 0 wCONSOLE=/dev/console TERM=linux SHELL=/bin/sh rootmnt=/root cpiorootsize= crashkernel=512M@128M image=/xxx/image1/ INIT_VERSION=sysvinit-2.88 init=/sbin/init COLUMNS=80 PATH=/xxx/sbin:/xxx/bin:/sbin:/usr/sbin:/bin:/usr/bin runlevel=2 RUNLEVEL=2 PWD=/root PREVLEVEL=N previous=N LINES=24 HOME=/ SHLVL=2 env=0x3DA97000 _=/sbin/shutdown 0 0 6764 6651 20 0 6304 600 pipe_w S+ pts/0 0:00 \_ grep shutdownTERM=xterm SHELL=/bin/bash SSH_CLIENT=172.16.92.39 49891 22 SSH_TTY=/dev/pts/0 USER=root MAIL=/var/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PWD=/root SHLVL=1 HOME=/root LOGNAME=root SSH_CONNECTION=172.16.92.39 49891 172.16.85.88 22 _=/bin/grep
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi All,
I noticed that if I disable the system TRIM from ext4 file system the reboot does not hang the system after reboot is issue, Also I have noticed that if the disk is full (SSD) and if system panics than core to /var/core directory doesn't complete and system hangs. The only work around to this problem is delete some previous core file for the present core to complete and system reboots. Please kindly let me know as why I am seeing these behaviors. For later I was expecting the core should be partially complete and system reboots as no disk space. Regards, Vipul.
participants (3)
-
Rajat Sharma -
Valdis.Kletnieks＠vt.edu -
Vipul Jain