Hello there,

I have some problems with my RAID-5 under gvinum since a power outage because of a lightning.

If I mount the volume and the automatic background fsck run, check or rebuild the parity I will get a panic.

Shorthand before the lightning I began to upgrade from 5.4-stable to 6.1-stable. Because of that I ignored the flaws on my data disk and continued the upgrade. The error originated with a 5.4-stable without debugging enabled.
Now the machine has the following running with a dump device configured:
FreeBSD titan.home.sumirati.net 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun Jul 30 21:19:10 CEST 2006 [EMAIL PROTECTED]:/usr/obj/ usr/src/sys/GENERIC i386

The stable is from Saturday, 29.07.2006 as of around 22:00 MET from cvsup2.de.freebsd.org.

The message in /var/crash/info.* looks everytime like this:
Panic String: kmem_malloc(262144): kmem_map too small: 172404736 total allocated

The dmesg and the vinum configuration is attached. I also attached a backtrace but I think it is not that useful.

I found nothing in the archives about a problem like this. Some PRs are showing kmem_map erros but not with (g)vinum.

My questions are:
Is there any know bug or problem with gvinum with rebuilding the parity? and
How can I get back my data? (of course :))

I'm in the process of making sure the hardware is ok while dd'ing them to /dev/null.

Thanks a lot for your time

Marc

Attachment: dmesg
Description: Binary data


titan# gvinum list
4 drives:
D wd120a State: up /dev/ad0s1 A: 33/114470 MB (0%) D wd120b State: up /dev/ad1s1 A: 33/114470 MB (0%) D wd120c State: up /dev/ad2s1 A: 2/114439 MB (0%) D wd120d State: up /dev/ad3s1 A: 33/114470 MB (0%)

1 volume:
V daten State: up Plexes: 1 Size: 335 GB

1 plex:
P daten.p0 R5 State: up Subdisks: 4 Size: 335 GB

4 subdisks:
S daten.p0.s3 State: up D: wd120d Size: 111 GB S daten.p0.s2 State: up D: wd120c Size: 111 GB S daten.p0.s1 State: up D: wd120b Size: 111 GB S daten.p0.s0 State: up D: wd120a Size: 111 GB

This GDB was configured as "i386-marcel-freebsd".

Unread portion of the kernel message buffer:
panic: kmem_malloc(262144): kmem_map too small: 172400640 total allocated
Uptime: 18h21m45s
Dumping 511 MB (2 chunks)
  chunk 0: 1MB (159 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15

#0  doadump () at pcpu.h:165
165             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0  doadump () at pcpu.h:165
#1 0xc0665e0e in boot (howto=260) at /usr/src/sys/kern/ kern_shutdown.c:409 #2 0xc06660a4 in panic (fmt=0xc08f0533 "kmem_malloc(%ld): kmem_map too small: %ld total allocated")
    at /usr/src/sys/kern/kern_shutdown.c:565
#3 0xc07d2f1d in kmem_malloc (map=0xc10430c0, size=262144, flags=258) at /usr/src/sys/vm/vm_kern.c:299 #4 0xc07ca852 in page_alloc (zone=0x0, bytes=262144, pflag=0x0, wait=258) at /usr/src/sys/vm/uma_core.c:958 #5 0xc07ccbab in uma_large_malloc (size=262144, wait=258) at /usr/ src/sys/vm/uma_core.c:2701 #6 0xc065b605 in malloc (size=262144, mtp=0xc0948ce0, flags=258) at / usr/src/sys/kern/kern_malloc.c:329
#7  0xc57907ea in ?? ()
#8  0x00040000 in ?? ()
#9  0xc0948ce0 in g_gptmodule_sys_init ()
#10 0x00000102 in ?? ()
#11 0xc389f200 in ?? ()
#12 0x4b2c0000 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00040000 in ?? ()
#15 0x00000000 in ?? ()
#16 0x00000000 in ?? ()
#17 0xe1880000 in ?? ()
#18 0xc5783380 in ?? ()
#19 0xc4b79e70 in ?? ()
#20 0xdeb71d10 in ?? ()
#21 0xc578d985 in ?? ()
#22 0xc3620600 in ?? ()
#23 0xc5783380 in ?? ()
#24 0xc4b8f108 in ?? ()
#25 0xcd5f6000 in ?? ()
#26 0xe1880000 in ?? ()
#27 0x00000003 in ?? ()
#28 0x00040000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00040000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00040000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0xcd6f4000 in ?? ()
#37 0xcd5f4000 in ?? ()
#38 0xc0667124 in sigprocmask (td=0xc3620600, uap=0xc4b96c60) at /usr/ src/sys/kern/kern_sig.c:700
Previous frame inner to this frame (corrupt stack?)
(kgdb)

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to