ss ? Like
>> ps -o flags
>
>
> Unfortunately I already rebooted this machine because our developers needed
> it and processes did not stop after kill -9.
>
> When this repeats, I will try to keep this server up for longer time and
> provide any necessary inform
> On 05 Mar 2016, at 21:35, Konstantin Belousov wrote:
>
> But I suspect that you do have enough free or reclamaible pages for OOM
> to not trigger, e.g. because you demonstrated commands output from the
> live system after the situation occured. It more likely was a temporal
> free page shorta
On Sat, Mar 05, 2016 at 07:42:51PM +0300, Dmitry Sivachenko wrote:
>
> > On 05 Mar 2016, at 19:27, Konstantin Belousov wrote:
> >
> > On Sat, Mar 05, 2016 at 05:24:26PM +0300, Dmitry Sivachenko wrote:
> >>>
> >>> Again, error 4 is EINTR so you could disable both "soft" and "intr"
> >>> options
> On 05 Mar 2016, at 19:27, Konstantin Belousov wrote:
>
> On Sat, Mar 05, 2016 at 05:24:26PM +0300, Dmitry Sivachenko wrote:
>>>
>>> Again, error 4 is EINTR so you could disable both "soft" and "intr" options
>>> for test.
>>
>>
>> "soft" is meaningless in such setup, because "file system c
On Sat, Mar 05, 2016 at 05:24:26PM +0300, Dmitry Sivachenko wrote:
> >
> > Again, error 4 is EINTR so you could disable both "soft" and "intr" options
> > for test.
>
>
> "soft" is meaningless in such setup, because "file system calls will fail
> after retrycnt round trip timeout intervals" bu
> On 05 Mar 2016, at 17:01, Eugene Grosbein wrote:
>
> 05.03.2016 20:42, Dmitry Sivachenko пишет:
>
>>> and to discover what version is broken. And show full mount command/option
>>> set.
>> I already included mount flags from fstab in my original e-mail:
>>
>> rw,bg,intr,soft
>
> If that's
05.03.2016 20:42, Dmitry Sivachenko пишет:
and to discover what version is broken. And show full mount command/option set.
I already included mount flags from fstab in my original e-mail:
rw,bg,intr,soft
If that's only options you use, there is another workaround: add options
rsize=1024,wsiz
gt;>> Sometimes I get the following messages in syslog:
>>>>
>>>> nfs_getpages: error 4
>>>> vm_fault: pager read error, pid NNN (myprog)
>>>>
>>>> After that I see I lot of processes stuck in "pfault" state (these are
>>
05.03.2016 19:32, Dmitry Sivachenko пишет:
I am running a number of machines with /home mounted via nfs (FreeBSD
10.3-PRERELEASE #0 r294799, rw,bg,intr,soft).
Sometimes I get the following messages in syslog:
nfs_getpages: error 4
vm_fault: pager read error, pid NNN (myprog)
After that I
etimes I get the following messages in syslog:
>>
>> nfs_getpages: error 4
>> vm_fault: pager read error, pid NNN (myprog)
>>
>> After that I see I lot of processes stuck in "pfault" state (these are
>> computational processes which use some files fro
05.03.2016 18:21, Dmitry Sivachenko пишет:
Hello,
I am running a number of machines with /home mounted via nfs (FreeBSD
10.3-PRERELEASE #0 r294799, rw,bg,intr,soft).
Sometimes I get the following messages in syslog:
nfs_getpages: error 4
vm_fault: pager read error, pid NNN (myprog)
After
Hello,
I am running a number of machines with /home mounted via nfs (FreeBSD
10.3-PRERELEASE #0 r294799, rw,bg,intr,soft).
Sometimes I get the following messages in syslog:
nfs_getpages: error 4
vm_fault: pager read error, pid NNN (myprog)
After that I see I lot of processes stuck in "p
12 matches
Mail list logo
