--
Dave Cherkus ----- UniMaster, Inc. ----- Contract Software Development
Specialties: UNIX TCP/IP X OSF/1 AlphaAXP AIX RS/6000 Performance ISDN
Email: cherkus_at_UniMaster.COM Tel: (603) 888-8308 Fax: (603) 888-8308
if (cpu.type == PENTIUM && cpu.step < 8) { panic("Intel Inside!"); }
From: MX%"BRENNAN_at_hal.hahnemann.edu" 17-FEB-1995 19:01:21.83
To: MX%"alpha-osf-managers_at_ornl.gov"
CC:
Subj: Impending crash dump
Return-Path: <alpha-osf-managers-relay_at_sws1.ctd.ornl.gov>
Received: from sws1.ctd.ornl.gov by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with SMTP;
Fri, 17 Feb 1995 19:01:18 EST
Received: (from daemon_at_localhost) by sws1.ctd.ornl.gov (8.6.9/8.6.9) id
SAA04710 for aomad; Fri, 17 Feb 1995 18:32:01 -0500
Sender: alpha-osf-managers-relay_at_sws1.ctd.ornl.gov
Received: from oaunx1.ctd.ornl.gov (oaunx1.ctd.ornl.gov [128.219.128.17]) by
sws1.ctd.ornl.gov (8.6.9/8.6.9) with ESMTP id SAA04622 for
<alpha-osf-managers_at_sws1.ctd.ornl.gov>; Fri, 17 Feb 1995 18:18:17
-0500
Received: from HAL.HAHNEMANN.EDU by oaunx1.ctd.ornl.gov (8.6.9/Ultrix3.0-C) id
SAA18158; Fri, 17 Feb 1995 18:18:11 -0500
Received: from hal.hahnemann.edu by hal.hahnemann.edu (PMDF V4.3-7 #8125) id
<01HN5YN9W2B8000QDQ_at_hal.hahnemann.edu>; Fri, 17 Feb 1995 18:18:56 EST
Date: Fri, 17 Feb 1995 18:18:56 -0500 (EST)
From: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_hal.hahnemann.edu>
Reply-To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_hal.hahnemann.edu>
Subject: Impending crash dump
To: alpha-osf-managers_at_ornl.gov
Message-ID: <01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
Followup-To: poster
X-VMS-To: MX%"alpha-osf-managers_at_ornl.gov"
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
In a Model 2000/300, we added 128Mb - up to 192Mb total. Normally, it's
great ... except we're still running OSF/1 v2.0b (with that little bug in
the ethernet driver) and crash occasionally.
Here's the problem. We crash, the system comes back up and attempts to
write a crash dump (a >200Mb file). It fails, but is holding onto the
fact that a crash dump file needs to be written the next time we reboot.
Anyone know what we need to do to clear that bit out? It delays the boot
a bit, but became a slightly more serious problem when we tried up upgrade
to v3.0b (we had problems during the upgrade attempt and have backed down
for the time being) ...
andrew. (brennan_at_hal.hahnemann.edu)
From: MX%"ebishop_at_vt.edu" 17-FEB-1995 19:41:36.65
To: MX%"BRENNAN_at_hal.hahnemann.edu"
CC:
Subj: Re: Impending crash dump
Return-Path: <ebishop_at_vt.edu>
Received: from seawolf.async.vt.edu by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with
SMTP; Fri, 17 Feb 1995 19:41:17 EST
Received: by seawolf.async.vt.edu; id AA03565; Fri, 17 Feb 1995 19:40:16 -0500
Date: Fri, 17 Feb 1995 19:40:15 -0500 (EST)
From: Eric Bishop <ebishop_at_vt.edu>
X-Sender: ebishop_at_seawolf.async.vt.edu
To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_hal.hahnemann.edu>
Subject: Re: Impending crash dump
In-Reply-To: <01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
Message-ID: <Pine.OSF.3.91.950217193925.3555A-100000_at_seawolf.async.vt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Fri, 17 Feb 1995, Andrew Brennan, Lackey-at-large wrote:
> Anyone know what we need to do to clear that bit out? It delays the boot
> a bit, but became a slightly more serious problem when we tried up upgrade
> to v3.0b (we had problems during the upgrade attempt and have backed down
> for the time being) ...
Try executing savecore -c
It will 'clear' the core dump without actually saving it.
__________________________ [ Virginia Tech ] __________________________
. Eric A. Bishop ebishop_at_vt.edu .
. Blacksburg, Virginia ebishop_at_csugrad.cs.vt.edu .
. U.S.A. http://csugrad.cs.vt.edu/~ebishop/ .
. ______________________________________________________ .
__________________ [ "Home of the Fighting Gobblers" ] __________________
______________________________________________________
From: MX%"scott_at_zk3.dec.com" 17-FEB-1995 19:50:27.81
To: MX%"BRENNAN_at_HAL.HAHNEMANN.EDU"
CC:
Subj: Re: Impending crash dump
Return-Path: <scott_at_zk3.dec.com>
Received: from decvax.dec.com by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with SMTP;
Fri, 17 Feb 1995 19:50:25 EST
Received: from styrax.zk3.dec.com by decvax.dec.com (5.65/DEC-ULTRIX-8/19/92)
id AA03892; Fri, 17 Feb 1995 19:49:11 -0500
Received: by alpha.zk3.dec.com; (5.65/1.1.8.2/15Sep94-0303PM) id AA13505; Fri,
17 Feb 1995 19:49:10 -0500
Date: Fri, 17 Feb 1995 19:49:10 -0500
From: Larry Scott USG <scott_at_zk3.dec.com>
Message-ID: <9502180049.AA13505_at_alpha.zk3.dec.com>
To: BRENNAN_at_HAL.HAHNEMANN.EDU
Subject: Re: Impending crash dump
andrew,
> Here's the problem. We crash, the system comes back up and attempts to
> write a crash dump (a >200Mb file). It fails, but is holding onto the
> fact that a crash dump file needs to be written the next time we reboot.
>
> Anyone know what we need to do to clear that bit out? It delays the boot
> a bit, but became a slightly more serious problem when we tried up upgrade
> to v3.0b (we had problems during the upgrade attempt and have backed down
> for the time being) ...
Use the "-c" option to savecore to mark the dump cleared.
What problem did you see on attempting to upgrade?
larry
From: MX%"alan_at_nabeth.cxo.dec.com" 17-FEB-1995 19:57:14.26
To: MX%"BRENNAN_at_HAL.HAHNEMANN.EDU"
CC:
Subj: Re: Impending crash dump
Return-Path: <alan_at_nabeth.cxo.dec.com>
Received: from inet-gw-1.pa.dec.com by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with
SMTP; Fri, 17 Feb 1995 19:57:12 EST
Received: from nabeth.cxo.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id
AA10081; Fri, 17 Feb 95 16:54:36 -0800
Received: by nabeth.cxo.dec.com (5.65/fma-100391); id AA23701; Fri, 17 Feb 1995
17:56:23 -0700
Message-ID: <9502180056.AA23701_at_nabeth.cxo.dec.com>
To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
Subject: Re: Impending crash dump
In-Reply-To: Your message of "Fri, 17 Feb 95 18:18:56 EST."
<01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
Date: Fri, 17 Feb 95 17:56:17 -0700
From: alan_at_nabeth.cxo.dec.com
X-Mts: smtp
See if the -c option of savecore does what you want.
From: MX%"ernie_at_MasPar.COM" 17-FEB-1995 21:36:37.97
To: MX%"BRENNAN_at_hal.hahnemann.edu"
CC:
Subj: Re: Impending crash dump
Return-Path: <ernie_at_MasPar.COM>
Received: from maspar.MasPar.COM by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with SMTP;
Fri, 17 Feb 1995 21:36:36 EST
Received: from armada by maspar.MasPar.COM (5.65/Ultrix3.0-C) id AA16472; Fri,
17 Feb 1995 18:29:37 -0800
Received: by armada.MasPar.COM (5.57/Ultrix2.0-B) id AA23205; Fri, 17 Feb 95
18:38:58 -0800
Received: by argosy.MasPar.COM (5.57/Ultrix2.4-C) id AA13062; Fri, 17 Feb 95
18:38:57 -0800
Received: by merlin.MasPar.Com (5.57/Ultrix2.4-C) id AA05151; Fri, 17 Feb 95
18:38:56 -0800
Date: Fri, 17 Feb 95 18:38:56 -0800
From: ernie_at_MasPar.COM (Ernie Rael)
Message-ID: <9502180238.AA05151_at_merlin.MasPar.Com>
To: BRENNAN_at_hal.hahnemann.edu
Subject: Re: Impending crash dump
> It fails, but is holding onto the
> fact that a crash dump file needs to be written the next time we reboot.
> Anyone know what we need to do to clear that bit out?
savecore(8) savecore(8)
NAME
savecore - Saves a core dump of the operating system
SYNOPSIS
savecore [-cefv] directory
The savecore command saves the most recent core dump of the system and
writes a reboot message in the shutdown log.
FLAGS
-c Does not copy the dump, but simply marks it invalid.
From: MX%"sarasin_at_yosemite.cop.dec.com" 19-FEB-1995 21:27:41.31
To: MX%"BRENNAN_at_HAL.HAHNEMANN.EDU"
CC:
Subj: Re: Impending crash dump
Return-Path: <sarasin_at_yosemite.cop.dec.com>
Received: from decuac.dec.com by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with SMTP;
Sun, 19 Feb 1995 21:27:39 EST
Received: from yosemite.cop.dec.com by decuac.dec.com;
(5.65/1.1.8.2/18Jan95-1237PM) id AA29071; Sun, 19 Feb 1995 21:26:36
-0500
Received: by yosemite.cop.dec.com; id AA20663; Sun, 19 Feb 1995 21:26:40 -0500
Message-ID: <9502200226.AA20663_at_yosemite.cop.dec.com>
To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
Subject: Re: Impending crash dump
In-Reply-To: Your message of "Fri, 17 Feb 95 18:18:56 EST."
<01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
Date: Sun, 19 Feb 95 21:26:40 -0500
From: sarasin_at_yosemite.cop.dec.com
X-Mts: smtp
Hello,
savecore -c should take care of your problem.
Sam S.
From: MX%"im_at_uvo.dec.com" 20-FEB-1995 02:21:24.13
To: MX%"BRENNAN_at_HAL.HAHNEMANN.EDU"
CC:
Subj: Re: Impending crash dump
Return-Path: <im_at_uvo.dec.com>
Received: from inet-gw-2.pa.dec.com by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with
SMTP; Mon, 20 Feb 1995 02:21:22 EST
Received: from decuk.uvo.dec.com by inet-gw-2.pa.dec.com (5.65/10Aug94) id
AA27440; Sun, 19 Feb 95 23:17:13 -0800
Received: from localhost by decuk.uvo.dec.com; (5.65/1.1.8.2/21Dec94-8.2MPM) id
AA23964; Mon, 20 Feb 1995 07:17:10 GMT
Message-ID: <9502200717.AA23964_at_uvo.dec.com>
To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
Subject: Re: Impending crash dump
In-Reply-To: Your message of "Fri, 17 Feb 95 18:18:56 EST."
<01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
Date: Mon, 20 Feb 95 07:17:03 +0000
From: "nagroM W sirdI" <im_at_uvo.dec.com>
X-Mts: smtp
Check out the manual page for savecore - I think you want to use either the -c
or -f flags....You should be able to do this from single user mode after a
reboot.
good luck!
regards
Idris Morgan
From: MX%"luchini_at_siberia.ups-tlse.fr" 20-FEB-1995 05:15:31.87
To: MX%"BRENNAN_at_HAL.HAHNEMANN.EDU"
CC:
Subj: Re: Impending crash dump
Return-Path: <luchini_at_siberia.ups-tlse.fr>
Received: from cix.cict.fr by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with SMTP; Mon,
20 Feb 1995 05:15:30 EST
Received: from siberia.ups-tlse.fr by cix.cict.fr; Mon, 20 Feb 95 11:15:56 +0100
Message-ID: <9502201015.AA03255_at_cix.cict.fr>
Received: by siberia.ups-tlse.fr; Mon, 20 Feb 95 11:13:45 GMT
Date: Mon, 20 Feb 95 11:13:45 GMT
From: luchini_at_siberia.ups-tlse.fr (Marco Luchini)
Posted-Date: Mon, 20 Feb 95 11:13:45 GMT
To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
Subject: Re: Impending crash dump
References: <01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
"Andrew Brennan, Lackey-at-large" writes:
> Here's the problem. We crash, the system comes back up and attempts to
> write a crash dump (a >200Mb file). It fails, but is holding onto the
> fact that a crash dump file needs to be written the next time we reboot.
From single user mode, when the machine is refusing to finish booting
because of the crash dump you can do:
# mount -u /
# bcheckrc
# /usr/sbin/rcmgr set SAVECORE_FLAGS M
# Control-D
Just the rcmgr command if you don't want to keep the possibility of
writing the core dump if there is space. You can also use rcmgr to
specify a different directory where to put your crash dump.
Ciao, Marco
-------------------------------------------------------------------------
Marco Luchini Internet : m.luchini_at_ic.ac.uk
Laboratoire de Physique Quantique Telephone: +33 61.55.60.39
Universite' Paul Sabatier Fax: +33 61.55.60.65
31062 Toulouse, FRANCE
-------------------------------------------------------------------------
From: MX%"Jonathan.J.B.Buchanan_at_Oda-3.CS.CSH.COM" 20-FEB-1995 05:37:42.32
To: MX%"brennan_at_hal.hahnemann.edu"
CC:
Subj: Impending crash dump
Return-Path: <Jonathan.J.B.Buchanan_at_Oda-3.CS.CSH.COM>
Received: from chsun.eunet.ch by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with SMTP;
Mon, 20 Feb 1995 05:37:40 EST
Received: from magnolia.eunet.ch by chsun.eunet.ch (8.6.4/1.34) id LAA11345;
Mon, 20 Feb 1995 11:37:04 +0100
From: Jonathan.J.B.Buchanan_at_Oda-3.CS.CSH.COM
X400-Received: by mta magnolia.eunet.ch in /PRMD=EUnet/ADMD=EUnet/C=CH/;
Relayed; Mon, 20 Feb 1995 11:45:12 +0100
X400-Received: by /PRMD=CSH/ADMD=ARCOM/C=CH/; Relayed; Mon, 20 Feb 1995
12:35:56 +0100
Date: Mon, 20 Feb 1995 12:35:56 +0100
X400-Originator: Jonathan.J.B.Buchanan_at_Oda-3.CS.CSH.COM
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=CSH/ADMD=ARCOM/C=CH/;74531102205991/139481_at_ZHPROD]
X400-Content-Type: P2-1984 (2)
Message-ID: <"65531102205991/47337 MRX*"_at_MHS>
To: brennan_at_hal.hahnemann.edu
Subject: Impending crash dump
Hello Andrew,
There was a note concerning a problem like the one you're
describing in the OSF/1 2.0 release notes (Installation
chapter).
It says to use 'savecore -c' in single user mode. Worth a
try?
Regards,
Jon Buchanan, Zuerich, Switzerland
[ Jonathan.Buchanan_at_cs.csh.com ]
From: MX%"jacy_at_fluid.mro.dec.com" 20-FEB-1995 10:53:46.99
To: MX%"BRENNAN_at_HAL.HAHNEMANN.EDU"
CC:
Subj: Re: Impending crash dump
Return-Path: <jacy_at_fluid.mro.dec.com>
Received: from inet-gw-1.pa.dec.com by HAL.HAHNEMANN.EDU (MX V4.0 VAX) with
SMTP; Mon, 20 Feb 1995 10:53:27 EST
Received: from fluid.mro.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id
AA00233; Mon, 20 Feb 95 07:45:36 -0800
Received: from localhost by fluid.mro.dec.com; (5.65/1.1.8.2/21Jan95-0912PM) id
AA27225; Mon, 20 Feb 1995 10:45:14 -0500
Message-ID: <9502201545.AA27225_at_fluid.mro.dec.com>
To: "Andrew Brennan, Lackey-at-large" <BRENNAN_at_HAL.HAHNEMANN.EDU>
Subject: Re: Impending crash dump
In-Reply-To: Your message of "Fri, 17 Feb 95 18:18:56 EST."
<01HN5YN9W2BA000QDQ_at_hal.hahnemann.edu>
Date: Mon, 20 Feb 95 10:45:14 -0500
From: jacy_at_fluid.mro.dec.com
X-Mts: smtp
Cut and pasting from the savecore man page........
Two options....
The default location for saving crash dumps is /var/adm/crash. This can be
overridden as follows:
/usr/sbin/rcmgr set SAVECORE_DIR directory
The default behavior of savecore is to return to single-user mode if it is
unable to save a core dump because of insufficient filesystem space. This
feature can be disabled as follows:
/usr/sbin/rcmgr set SAVECORE_FLAGS M
Jacy Canute
Received on Tue Feb 21 1995 - 11:35:37 NZDT
This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:45 NZDT