Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: /sbin/kexec became zero size... Anyone else?
Date: Tue, 23 Sep 2008 09:41:50 -0700	[thread overview]
Message-ID: <48D91C4E.5030704@sgi.com> (raw)
In-Reply-To: <20080923075202.GA20108@verge.net.au>

Simon Horman wrote:
> On Wed, Sep 17, 2008 at 02:07:15PM -0700, Jay Lan wrote:
>> Hi,
>>
>> My root disk was populated with sles10sp2, but the kernel was
>> 2.6.27-rc5 and /sbin/kexec was built from 2.0.0 version.
>>
>> Many times when kdump kernel failed early i found  after reboot that
>> /sbin/kexec became zero size. There was no warning on executing
>> '/etc/init.d/kdump start' when /sbin/kexec is zero size. I have
>> no idea when and how that happened.
>>
>> Has anyone else seen this problem?
> 
> Is it possible that this is caused by filesystem corruption?

I found the problems, which i can not reliably reproduce, happened
when i ran into kdump kernel boot failure (yet not every time.)
What puzzled me was why only /sbin/kexec was affected.

I can not explain what caused it (otherwise i would be able to
reproduce it) and do not know where my finger should point to. ;)
The good news is since i fixed the kernel boot problem it has not
happened any more.

The distros probably can add a check against zero-sized kexec
in /etc/init.d/kdump script though.

Thanks,
 - jay


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-09-23 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 21:07 /sbin/kexec became zero size... Anyone else? Jay Lan
2008-09-23  7:52 ` Simon Horman
2008-09-23 16:41   ` Jay Lan [this message]
2008-09-23 17:41     ` Neil Horman
2008-09-23 20:32       ` Jay Lan
2008-09-23 20:41         ` Neil Horman
2010-04-08 16:54         ` Neil Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48D91C4E.5030704@sgi.com \
    --to=jlan@sgi.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox