2010/1/14 Doug Poland :
>
> On Thu, January 14, 2010 08:50, Ivan Voras wrote:
>> 2010/1/14 Doug Poland :
>
> kstat.zfs.misc.arcstats.size
>
> seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
> during this last run
Is that with or without panicking?
>>
On Thu, January 14, 2010 08:50, Ivan Voras wrote:
> 2010/1/14 Doug Poland :
kstat.zfs.misc.arcstats.size
seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
during this last run
>>>
>>> Is that with or without panicking?
>>>
>> with a panic
>>
>>
>>> If the
2010/1/14 Doug Poland :
>
> On Thu, January 14, 2010 03:17, Ivan Voras wrote:
>> Doug Poland wrote:
>
Ok, I re-ran with same config, but this time monitoring the
sysctls you requested* ( and the rest I was watching ):
>>> I failed to mention that
>>>
>>> kstat.zfs.misc.arcstats.s
On Thu, January 14, 2010 03:17, Ivan Voras wrote:
> Doug Poland wrote:
>>> Ok, I re-ran with same config, but this time monitoring the
>>> sysctls you requested* ( and the rest I was watching ):
>>>
>> I failed to mention that
>>
>> kstat.zfs.misc.arcstats.size
>>
>> seemed to fluctuate betwe
Doug Poland wrote:
Ok, I re-ran with same config, but this time monitoring the sysctls
you requested* ( and the rest I was watching ):
I failed to mention that
kstat.zfs.misc.arcstats.size
seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
during this last run
Is that
>>
>>
> Ok, I re-ran with same config, but this time monitoring the sysctls
> you requested* ( and the rest I was watching ):
>
I failed to mention that
kstat.zfs.misc.arcstats.size
seemed to fluctuate between about 164,000,00 and 180,000,000 bytes
during this last run
--
Regards,
Doug
_
On Wed, January 13, 2010 13:57, Ivan Voras wrote:
> 2010/1/13 Doug Poland :
>>
>
> Can you monitor and record kstat.zfs.misc.arcstats.size sysctl while
> the test is running (and crashing)?
>
> This looks curious - your kmem_max is ~~ 1.2 GB, arc_max is 0.5 GB and
> you are still having panics. Is
On Wed, January 13, 2010 13:57, Ivan Voras wrote:
> 2010/1/13 Doug Poland :
>> This is the state of the machine when it panicked this time:
>>
>> panic: kmem_malloc(131072): kmem_map too small: 1296957440 total
>> allocated
>> cpuid = 1
>>
>> /boot/loader.conf: vfs.zfs.arc_max=512M
>> vfs.numvnod
2010/1/13 Doug Poland :
>
> On Wed, January 13, 2010 12:35, Ivan Voras wrote:
Try adding vfs.zfs.arc_max=512M to /boot/loader.conf.
>>> Would you suggest tweaking the vm.kmem_size tunables in addition to
>>> arc_max?
>>
>> No, unless they auto-tune to something lesser than approximat
On Wed, January 13, 2010 12:35, Ivan Voras wrote:
>>>
>>> Try adding vfs.zfs.arc_max=512M to /boot/loader.conf.
>>>
>> Would you suggest tweaking the vm.kmem_size tunables in addition to
>> arc_max?
>
> No, unless they auto-tune to something lesser than approximately
> arc_max*3.
>
> I try to set
2010/1/13 Doug Poland :
>
> On Wed, January 13, 2010 11:55, Ivan Voras wrote:
>> Doug Poland wrote:
>>
>>> So the question is, can ZFS be tuned to not panic or hang no matter
>>> what I throw at it?
>>
>> Apparently not.
>>
>> > I began with a system with no tunables in /boot/loader.conf
>> > (vm
On Wed, January 13, 2010 11:55, Ivan Voras wrote:
> Doug Poland wrote:
>
>> So the question is, can ZFS be tuned to not panic or hang no matter
>> what I throw at it?
>
> Apparently not.
>
> > I began with a system with no tunables in /boot/loader.conf
> > (vm.kmem_size and vm.kmem_size_max). T
Doug Poland wrote:
So the question is, can ZFS be tuned to not panic or hang no matter
what I throw at it?
Apparently not.
> I began with a system with no tunables in /boot/loader.conf
> (vm.kmem_size and vm.kmem_size_max). Then I tried increasing
> vm.kmem_size and vm.kmem_size_max a GB at
Hello,
I'm trying to get an 8.0-RELEASE-p2 amd64 box to not crash when
running benchmarks/unixbench. The box in question has 4GB RAM running
6 SCSI disks in a RAID1Z.
dmesg | grep memory
real memory = 4294967296 (4096 MB)
avail memory = 3961372672 (3777 MB)
zpool status
pool: bethesda
state
14 matches
Mail list logo
