Re: why kexec insists on syncing with recent kernels?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Vivek Goyal
Date: Thursday, February 7, 2008 - 9:37 am

On Thu, Feb 07, 2008 at 03:13:30PM +0100, Tomasz Chmielewski wrote:

In latest kexec code I do see it syncing. But it does not unmount the
filesystems. So this comment looks like partially wrong.


Which kexec-tools you are using? 

syncing is initiated by user space so changing kernel will not have
any effect (as long as user space is same). I think just that message
are spitted by kernel, so probably 2.6.18 did not spit any message and
2.6.24 does.


Kexec has got an option -x --no-ifdown, which will not bring the network
down. Try that. "kexec- -e -x"



To me it makes sense. Just making sure that cache changes make to the file
system before you boot into new kernel.

In latest kexec-tools, I do see sync() is done first and then network
interfaces are brought down. 

Try latest kexec tools from:

http://www.vergenet.net/~horms/linux/kexec/kexec-tools/testing/kexec-tools-testing-200...

and see if it works fine for you.

Thanks
Vivek
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
why kexec insists on syncing with recent kernels?, Tomasz Chmielewski, (Thu Feb 7, 7:13 am)
Re: why kexec insists on syncing with recent kernels?, Vivek Goyal, (Thu Feb 7, 9:37 am)
Re: why kexec insists on syncing with recent kernels?, Tomasz Chmielewski, (Thu Feb 7, 9:59 am)
Re: why kexec insists on syncing with recent kernels?, Geert Uytterhoeven, (Fri Feb 8, 1:53 am)
Re: why kexec insists on syncing with recent kernels?, Randy Dunlap, (Fri Feb 8, 10:04 am)
Re: why kexec insists on syncing with recent kernels?, Tomasz Chmielewski, (Fri Feb 8, 10:19 am)
Re: why kexec insists on syncing with recent kernels?, Vivek Goyal, (Fri Feb 8, 10:26 am)
Re: why kexec insists on syncing with recent kernels?, Geert Uytterhoeven, (Mon Feb 11, 5:36 am)