NetBSD Problem Report #18419
Received: (qmail 9574 invoked by uid 605); 25 Sep 2002 18:45:12 -0000
Message-Id: <200209251845.g8PIj8w00495@gamera.mt.sri.com>
Date: Wed, 25 Sep 2002 12:45:08 -0600 (MDT)
From: chris@cjones.org
Sender: gnats-bugs-owner@netbsd.org
Reply-To: chris@cjones.org
To: gnats-bugs@gnats.netbsd.org
Subject: can't dump to a RAIDframe device
X-Send-Pr-Version: 3.95
>Number: 18419
>Category: port-i386
>Synopsis: can't dump to a RAIDframe device
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-i386-maintainer
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Sep 25 18:46:00 +0000 2002
>Closed-Date: Thu Apr 01 17:58:40 +0000 2004
>Last-Modified: Thu Apr 01 17:58:40 +0000 2004
>Originator: Chris Jones
>Release: NetBSD 1.6
>Organization:
chris@mt.sri.com -----------------------------------------------------
Chris Jones SRI International, Inc.
www.mt.sri.com www.sri.com
>Environment:
System: NetBSD gamera.mt.sri.com 1.6 NetBSD 1.6 (GAMERA) #0: Mon Sep 23 16:47:30 MDT 2002 chris@legolas.mt.sri.com:/usr/src/sys/arch/i386/compile/GAMERA i386
Architecture: i386
Machine: i386
Configuration follows:
total memory = 127 MB
avail memory = 115 MB
pciide0 at pci0 dev 7 function 1: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
wd0 at pciide0 channel 0 drive 0: <Maxtor 5T060H6>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 58644 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 120103200 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
pciide0: secondary channel wired to compatibility mode
pciide0: disabling secondary channel (no drives)
pciide1 at pci0 dev 14 function 0: Promise Ultra100/ATA Bus Master IDE Accelerator (rev. 0x02)
pciide1: bus-master DMA support present
pciide1: primary channel configured to native-PCI mode
pciide1: using irq 9 for native-PCI interrupt
wd1 at pciide1 channel 0 drive 0: <MAXTOR 6L080J4>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 76345 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 156355584 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6
wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
pciide1: secondary channel configured to native-PCI mode
wd2 at pciide1 channel 1 drive 0: <MAXTOR 6L080J4>
wd2: drive supports 16-sector PIO transfers, LBA addressing
wd2: 76345 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 156355584 sectors
wd2: 32-bit data port
wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6
wd2(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
gamera# raidctl -s raid0
Components:
/dev/wd2e: optimal
/dev/wd1e: optimal
gamera# cat /etc/fstab
/dev/raid0a / ffs rw,softdep 1 1
/dev/wd1a /altroot ffs rw,softdep 1 2
/dev/wd2a /altroot2 ffs rw,softdep 1 2
/dev/raid0b none swap sw 0 0
/dev/raid0b none swap dp 0 0
/dev/raid0b /tmp mfs rw 0 0
/dev/raid0e /usr ffs rw,softdep 1 2
/dev/raid0h /users ffs rw,softdep 1 2
/dev/raid0g /data ffs rw,softdep 1 3
/dev/raid0f /var ffs rw,softdep 1 4
/dev/wd0e /stage ffs rw,softdep 1 2
/kern /kern kernfs rw 0 0
/dev/fd0a /floppy msdos rw,noauto 0 0
gamera# disklabel raid0
...
# size offset fstype [fsize bsize cpg/sgs]
a: 140032 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 546)
b: 2097152 140032 swap # (Cyl. 547 - 8738)
c: 156055136 0 unused 0 0 # (Cyl. 0 - 609590*)
d: 156055136 0 unused 0 0 # (Cyl. 0 - 609590*)
e: 4194304 2237184 4.2BSD 1024 8192 16 # (Cyl. 8739 - 25122)
f: 41943040 6431488 4.2BSD 1024 8192 16 # (Cyl. 25123 - 188962)
g: 25165824 48374528 4.2BSD 1024 8192 16 # (Cyl. 188963 - 287266)
h: 82514784 73540352 4.2BSD 1024 8192 32 # (Cyl. 287267 - 609590*)
>Description:
When the machine tries to write a crash dump to raid0b, it fails.
It says, "dumping to dev x,y offset z", followed by,
"dump device bad".
>How-To-Repeat:
Entering ddb and typing "sync" does the trick. Actually, it panics the
machine.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: chris@cjones.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/18419: can't dump to a RAIDframe device
Date: Wed, 25 Sep 2002 22:45:56 +0200
On Wed, Sep 25, 2002 at 12:45:08PM -0600, chris@cjones.org wrote:
> >Description:
> When the machine tries to write a crash dump to raid0b, it fails.
> It says, "dumping to dev x,y offset z", followed by,
> "dump device bad".
I think this is almost impossible to solve because raidframe uses a kernel
thread, which is basically unavailable at this point (process scheduling
stopped). But there is a workaround: define a swap partition on one of
the disk (if you're using a raid1, you can define it to be at the same
place as in the raid1 - but beware: you need to do the maths starting
from the end of the disks and partitions, not from start, because
raidframe reserve some space at the beggining).
Then define this partition as dump device in the fstab.
--
Manuel Bouyer <bouyer@antioche.eu.org>
--
From: Roland Dowdeswell <elric@imrryr.org>
To: chris@cjones.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/18419: can't dump to a RAIDframe device
Date: Wed, 25 Sep 2002 18:49:40 -0400
On 1032979508 seconds since the Beginning of the UNIX epoch
chris@cjones.org wrote:
>
>>Synopsis: can't dump to a RAIDframe device
>When the machine tries to write a crash dump to raid0b, it fails.
>It says, "dumping to dev x,y offset z", followed by,
>"dump device bad".
>>How-To-Repeat:
>Entering ddb and typing "sync" does the trick. Actually, it panics the
>machine.
Yes, this feature is unimplemented on any of our pseudo-disks as of
yet.
--
Roland Dowdeswell http://www.Imrryr.ORG/~elric/
State-Changed-From-To: open->closed
State-Changed-By: tls
State-Changed-When: Thu Apr 1 17:57:23 UTC 2004
State-Changed-Why:
Duplicates PR 17322.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.