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 "pfault"
Bezüglich John Baldwin's Nachricht vom 02.03.2016 18:32 (localtime):
> On Monday, February 29, 2016 07:29:03 PM Harry Schmalzbauer wrote:
>> Bezüglich Harry Schmalzbauer's Nachricht vom 28.02.2016 20:55 (localtime):
>>> Hello,
>>>
>>> I have a remote machine with a probably defective ODD, but unt
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 tha
On 03 Mar 2016, at 14:45, kpn...@pobox.com wrote:
>
> I notice on 10.2 we're using "FreeBSD clang version 3.4.1". But there are
> bugs in this version of clang that I'm having trouble with.
Which specific bugs are those?
> Is compiling a newer (say, 3.7.1) version of clang to target FreeBSD
> s
On 04 Mar 2016, at 15:53, Kevin P. Neal wrote:
>
> On Fri, Mar 04, 2016 at 02:22:26PM +, Brooks Davis wrote:
>> On Thu, Mar 03, 2016 at 08:45:05AM -0500, kpn...@pobox.com wrote:
>>> I notice on 10.2 we're using "FreeBSD clang version 3.4.1". But there are
>>> bugs in this version of clang tha
> On 05 Mar 2016, at 15:13, Eugene Grosbein wrote:
>
> 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:
>>
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 see
> On 05 Mar 2016, at 16:33, Eugene Grosbein wrote:
>
> 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:
>
Hi,
Could someone with enough knowledge please look into
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207714 and fix it
before 10.3?
It is rather nasty as it corrupts files with holes when doing 'zfs
send/zfs receive'. Such files appear 'automatically' if compression is
enabled and a large e
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
> 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
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 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 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 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 Saturday, March 05, 2016 01:11:13 PM Harry Schmalzbauer wrote:
> Bezüglich John Baldwin's Nachricht vom 02.03.2016 18:32 (localtime):
> > On Monday, February 29, 2016 07:29:03 PM Harry Schmalzbauer wrote:
> >> Bezüglich Harry Schmalzbauer's Nachricht vom 28.02.2016 20:55 (localtime):
> >>> Hel
Bezüglich John Baldwin's Nachricht vom 05.03.2016 22:50 (localtime):
> On Saturday, March 05, 2016 01:11:13 PM Harry Schmalzbauer wrote:
>> Bezüglich John Baldwin's Nachricht vom 02.03.2016 18:32 (localtime):
…
>> With BETA3-iso, where booting fails, "random: unblocking device."
>> happens after ti
17 matches
Mail list logo