Re: Panic on evbarm triggered by dumpfs

[Petri Laakso <petri.laakso%asd.fi@localhost>]

On Wed, 15 Jan 2014, Petri Laakso wrote:

> On Wed, 15 Jan 2014, Christos Zoulas wrote:
>
> > In article <20140114222621.1e157cd83dafaebb495f1bb3%asd.fi@localhost>,
> > Petri Laakso  <petri.laakso%asd.fi@localhost> wrote:
> > > On Tue, 14 Jan 2014 22:14:01 +0200
> > > Petri Laakso <petri.laakso%asd.fi@localhost> wrote:
> > >
> > > > Hi all!
> > > >
> > > > Today I made fresh install of evbarm from current sources. I am able to
> > > > trigger panics after I use dumpfs command. I am able to use the system
> > >
> > > Forgot to include fstab:
> > >
> > > #evbarm cat /etc/fstab
> > >
> > > /dev/ld0a       /       ffs     rw,log,noatime  1 1
> > > /dev/ld0b       none    swap    sw,dp   0 0
> > > ptyfs   /dev/pts        ptyfs   rw
> > > kernfs          /kern   kernfs  rw
> > > procfs          /proc   procfs  rw
> >
> >
> > Show fdisk and disklabel output. Something is overwriting your partition.
>
> [fdisk & disklabel output removed]

I took little sample of NetBSD partition to see what it has. It looks
like this:

evbarm# dd if=/dev/rld0a bs=1k of=/var/tmp/rld0a_1k.data count=1
evbarm# hexdump -C /var/tmp/rld0a_1k.data
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000200  57 45 56 82 04 00 00 00  53 54 4f 52 41 47 45 20  |WEV.....STORAGE |
00000210  44 45 56 49 43 45 20 20  66 69 63 74 69 74 69 6f  |DEVICE  fictitio|
00000220  75 73 00 00 00 00 00 00  00 02 00 00 20 00 00 00  |us.......... ...|
00000230  40 00 00 00 80 07 00 00  00 08 00 00 00 00 3c 00  |@.............<.|
00000240  00 00 00 00 00 00 00 00  10 0e 01 00 00 00 00 00  |................|
00000250  00 00 00 00 00 00 00 00  01 00 00 00 00 00 00 00  |................|
00000260  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000280  00 00 00 00 57 45 56 82  50 fc 06 00 00 20 00 00  |....WEV.P.... ..|
...