David Bond wrote: > thanks for the help, i just took a look in the /var/crash/ directory and it > appear the server crashed again 2 days ago, so there is now a dump (as > savecore was then enabled) so here is the output from the mdb -k 0 > > r...@nas:/var/crash/NAS# /usr/bin/mdb -k 0 > Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp > rootnex scsi_vhci zfs sockfs ip hook neti sctp arp usba uhci fctl md lofs > random sata fcp fcip cpc sd crypto smbsrv nfs logindmux ptm ufs sppp nsmb ipc > ] >> $c > page_create_va+0x314(fffffffffbc30210, ffffff01ec018000, 300000, 13, > ffffff0004e675d0, ffffff01ec018000) > segkmem_page_create+0x8d(ffffff01ec018000, 300000, 0, fffffffffbc30210) > segkmem_xalloc+0xc0(ffffff0146e07000, 0, 300000, 0, 0, fffffffffb880cb8) > segkmem_alloc_vn+0xcd(ffffff0146e07000, 300000, 0, fffffffffbc30210) > segkmem_alloc+0x24(ffffff0146e07000, 300000, 0) > vmem_xalloc+0x546(ffffff0146e0d000, 300000, 1000, 0, 0, 0) > vmem_alloc+0x161(ffffff0146e0d000, 300000, 0) > kmem_alloc+0x60(300000, 0) > kmem_zalloc+0x3b(300000, 0) > auto_calldaemon+0x22d(0, 0, fffffffffbb184e8, 0, fffffffffbb184e8, 0) > auto_null_request+0x3d(ffffff0150402d40, 0) > unmount_tree+0x126(ffffff0150156950, 0) > unmount_zone_tree+0x1e(ffffff0150156950) > thread_start+8()
You'll probably need to do a little more poking around than that. The call stack doesn't seem to implicate anything related to that driver -- though it's certainly possible that the problem is the result of memory corruption. Look at "::status" and "::kmem_verify" in mdb. You'll need to try to figure out what the system was doing when it went down. The stack above suggests autofs, but perhaps it's just the victim here. If the system is unstable, it might be possible to turn on some of the kmem debugging options via /etc/system to cause it to crash earlier, and thus provide a clearer picture of what's going wrong. -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ networking-discuss mailing list [email protected]
