Date: Thu, 27 Aug 2009 12:16:20 +0200 From: Olivier Smedts <olivier@gid0.org> To: "Mikhail (Plus Plus)" <m@plus-plus.su> Cc: freebsd-fs@freebsd.org Subject: Re: need help with ZFS Message-ID: <367b2c980908270316n7a21673ek3a997573f2fadbb0@mail.gmail.com> In-Reply-To: <4A9656CE.8020107@plus-plus.su> References: <4A927CB3.3040402@plus-plus.su> <4A964F4E.4080009@plus-plus.su> <4A9656CE.8020107@plus-plus.su>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/8/27 Mikhail (Plus Plus) <m@plus-plus.su>: > Mikhail (Plus Plus) wrote: >> >> Everything worked fine for about ~90 minutes, but then system paniced. I >> got escaped to "db> " prompt on local console, but I have zero debugging >> experience, so I just rebooted the server. The only thing I noticed was = that >> last mentioned PID on the panic screen was bonnie++'s process. > > Ok, I just ran bonnie++ test on ZFS (no rsync this time, only bonnie++) a= nd > system paniced again after ~23 minutes. Right now I see the following on > local console: > > "Memory modified after free 0xffff... val=3D... @ 0xff.. > panic: Most recently used by solaris > cpuid =3D 1 > KDB: enter: panic > [thread pid 883 tid 10.. ] > Stopped at =A0 =A0 =A0kdb_enter 0x3d: movq =A0 =A0...(%rip) > db> " You can output the backtrace by entering "bt" at the "db> "prompt. > and PID 883 was bonnie++'s PID before system panic. > > Mikhail. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?367b2c980908270316n7a21673ek3a997573f2fadbb0>