Subject: bin/15947: savecore wont (on secondary swap partitions)
To: None <gnats-bugs@gnats.netbsd.org>
From: Frank Kardel <kardel@acm.org>
List: netbsd-bugs
Date: 03/17/2002 16:35:45
>Number: 15947
>Category: bin
>Synopsis: savecore fails to find core on alternate dump device (e.g. wd1b instead of wd0b)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Mar 17 07:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Frank Kardel
>Release: NetBSD 1.5ZB
>Organization:
>Environment:
System: NetBSD pip 1.5ZB NetBSD 1.5ZB (PIP) #0: Sun Mar 10 21:45:27 MET 2002 kardel@pip:/fs/IC35L060-0-a/src/NetBSD/netbsd/sys/arch/i386/compile/PIP i386
Architecture: i386
Machine: i386
>Description:
After a panic dump onto /dev/wd1b (instead of /dev/wd0b as usual target) savecore
claims that no coredump exists. Non standard dump location is
chossen because image wouldn't fit on /dev/wd0b.
ktruss showed that savecore actuall attempts to access /dev/wd1b but it
decides that no core file exists.
>How-To-Repeat:
fstab (only swap related stuff):
/dev/wd0b none swap sw
/dev/wd1b none swap sw
/dev/wd1b none swap dp
/dev/wd2b none swap sw
Rest ist standard. force kernel dump (should go onto /dev/wd1b (dev 0,9))
watch savecore announcing "no coredump" 8-(
>Fix:
check kernel coredump/savecore logic?
>Release-Note:
>Audit-Trail:
>Unformatted: