Tue, 04 Mar 2008 03:27:35 +0800，Xin LI <[EMAIL PROTECTED]>:
The kernel is
FreeBSD fs12.sina.com.cn 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun Mar 2
18:50:05 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZFORK
amd64
the get all at below:
fs12# zfs get all
NAME PROPERTY VALUE
Pawel Jakub Dawidek wrote:
> On Sun, Mar 02, 2008 at 03:49:03AM -0800, LI Xin wrote:
>> Hi,
>>
>> The following iozone test case on ZFS would reliably trigger panic:
>>
>> /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -R -r 4k -s 30g
>> -i 0 -i 1 -i 2 -i 8 -+p 70 -C
>
> Thanks, I'll try
On Sun, Mar 02, 2008 at 03:49:03AM -0800, LI Xin wrote:
> Hi,
>
> The following iozone test case on ZFS would reliably trigger panic:
>
> /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -R -r 4k -s 30g
> -i 0 -i 1 -i 2 -i 8 -+p 70 -C
Thanks, I'll try to reproduce it.
[...]
> #19 0x000
LI Xin wrote:
> Hi,
>
> The following iozone test case on ZFS would reliably trigger panic:
>
> /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -R -r 4k -s 30g
> -i 0 -i 1 -i 2 -i 8 -+p 70 -C
It can also be (eventually) triggered by "blogbench -c 100 -i 30 -r 50
-w 10 -W 10" and heavy IO
Hi,
The following iozone test case on ZFS would reliably trigger panic:
/usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -R -r 4k -s 30g
-i 0 -i 1 -i 2 -i 8 -+p 70 -C
Unfortunately the kgdb can not reveal useful backtrace. I have tried
KDB_TRACE, but have not yet be able to further i
