> On May 4, 2015, at 5:45 PM, Chris Siebenmann wrote:
>
>
> Is there any way to limit the number of pending NFS requests that the
> system will accept? Allowing 270,000 strikes me as kind of absurd.
I swear I've seen someone try to address this before. Maybe it's from my
Nexenta days. I wil
Yes, absolutely. We've run into this same problem, exactly as you
describe, in Solaris10 (all versions)
You can catch it with a kernel dump, but you have to be wary and quick.
keep a vmstat 3 open (or similar), and when free mem drops below 5GB or
so, be ready. As soon you start seeing PO or DE
We now have a reproducable setup with OmniOS r151014 where an OmniOS
NFS fileserver will experience memory exhaustion and then hang in the
kernel if it receives sustained NFS write traffic from multiple clients
at a rate faster than its local disks can sustain. The machine will run
okay for a whil
Yeah, me too now! Thanks Dan.
On Mon, May 4, 2015 at 7:43 PM, Dan McDonald wrote:
>
>> On May 4, 2015, at 1:10 PM, Davide Poletto wrote:
>>
>> Just to say I've noticed that uname -v reports "illumos-omnios" on a
>> OmniOS 151012 which was "omnios-10b9c79" after I updated it today
>> (packages re
> On May 4, 2015, at 1:10 PM, Davide Poletto wrote:
>
> Just to say I've noticed that uname -v reports "illumos-omnios" on a
> OmniOS 151012 which was "omnios-10b9c79" after I updated it today
> (packages released on 17.04.2015 at official repository):
>
> OmniOS 5.11 omnios-10b9c79 Septem
Just to say I've noticed that uname -v reports "illumos-omnios" on a
OmniOS 151012 which was "omnios-10b9c79" after I updated it today
(packages released on 17.04.2015 at official repository):
OmniOS 5.11 omnios-10b9c79 September 2014
root@nas:/root#
OmniOS 5.11 illumos-omnios April 201
