public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Preben Traerup <Preben.Trarup@ericsson.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [PATCH] kdump: add a missing notifier before crashing
Date: Mon, 19 Jun 2006 15:28:23 +0200	[thread overview]
Message-ID: <4496A677.3020301@ericsson.com> (raw)
In-Reply-To: <m1y7vtia7r.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:

>"Akiyama, Nobuyuki" <akiyama.nobuyuk@jp.fujitsu.com> writes:
>
>  
>
>>On Fri, 16 Jun 2006 10:37:05 -0600
>>ebiederm@xmission.com (Eric W. Biederman) wrote:
>>
>>    
>>
>>>>The processing of the notifier is to make a SCSI adaptor power off to
>>>>stop writing in the shared disk completely and then notify to standby-node.
>>>>        
>>>>
>>>The kernel has called panic no new SCSI operations were execute.
>>>I'm not saying don't notify your standby-node
>>>      
>>>
>>As you say, the kernel does not do anything about SCSI operations.
>>But many SCSI adaptors flush their cache after a few seconds pass
>>after a SCSI write command is invoked, especially RAID cards.
>>To completely stop writing immediately, we should make the adaptor
>>power off.
>>    
>>
>
>Yes.  Although I don't have a clue what big scsi has to do with a
>telco systems.
>  
>
Strictly speaking for myself: Nothing.

Mr. Akiyama Nobuyuk gave an example from his environment which is cluster systems.
I was the one saying we in our Telco systems could use this feature too.

The only thing Mr. Akiyama Nobuyuk and I have in common is we both would like to do
something before crash dumping, simply because the less mess we will have to cleanup
afterwards in the system taking over, the better.

Mr. Akiyama Nobuyuk operates on SCSI devices to avoid filesystem corruptions.
My usage would be more like notifying external management to get traffic 
redirected to server systems taking over.

./Preben




  reply	other threads:[~2006-06-19 13:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15 11:16 [PATCH] kdump: add a missing notifier before crashing Akiyama, Nobuyuki
2006-06-16  6:28 ` [Fastboot] " Eric W. Biederman
2006-06-16 12:15   ` Akiyama, Nobuyuki
2006-06-16 16:37     ` Eric W. Biederman
2006-06-19  7:30       ` Akiyama, Nobuyuki
2006-06-19 12:47         ` Eric W. Biederman
2006-06-19 13:28           ` Preben Traerup [this message]
2006-06-19 16:49             ` Eric W. Biederman
2006-06-19 17:07               ` Vivek Goyal
2006-06-19 17:50                 ` Eric W. Biederman
2006-06-19 18:19                   ` Vivek Goyal
2006-06-19 18:45                     ` Eric W. Biederman
2006-06-20  3:46                   ` Akiyama, Nobuyuki
2006-06-20  3:39             ` Akiyama, Nobuyuki
  -- strict thread matches above, loose matches on Subject: below --
2006-07-04 12:33 Akiyama, Nobuyuki
2006-07-05 16:14 ` [Fastboot] " Eric W. Biederman

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=4496A677.3020301@ericsson.com \
    --to=preben.trarup@ericsson.com \
    --cc=akiyama.nobuyuk@jp.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.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