gvinum and raid5

[Nicolae Namolovan]

On Nov 5 09:36:55 PST 2007, Marco Haddad <freebsd-lists at ideo.com.br> wrote:
>Well, I can't do that because 'gvinum create'  panics even if the new drive
>is named differently. Perhaps the problem is using the same device which was
>once already present, and that's why I need to remove all objects first...

Same happened here..

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x40
fault code              = supervisor read data, page not present
instruction pointer     = 0x8:0xffffffffb03de982
stack pointer           = 0x10:0xffffffffac105710
frame pointer           = 0x10:0xffffffffac105740
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 2 (g_event)
trap number             = 12
panic: page fault
cpuid = 0


How to reproduce ?

For example you had already
drive d1 device /dev/ad12s1e

d1 for some reason is not working anymore, after you trying to add
drive d1_new device /dev/ad12s1e

Put that to a separate file, gvinup create file, and boom, kernel panic..

-- 
Sincerely,
Nicolae Namolovan.