Date: Sun, 20 Jan 2013 17:24:59 -0800 From: Marc Fournier <scrappy@hub.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: 9-STABLE -> NFS -> NetAPP: Message-ID: <F3AD6C5A-A263-4A9A-9485-D9CB8821C35A@hub.org> In-Reply-To: <201301200947.11580.jhb@freebsd.org> References: <B7529290-01FC-4E14-ACE5-1EBFCF2367C3@hub.org> <201301190757.26398.jhb@freebsd.org> <7387292F-94CD-4643-91D4-748404B792F1@hub.org> <201301200947.11580.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yup, saw those commits =85am going through the servers and doing =
upgrades on them =85 will report on any issues post-upgrade =85
thx
On 2013-01-20, at 6:47 AM, John Baldwin <jhb@freebsd.org> wrote:
> On Sunday, January 20, 2013 01:10:29 AM Hub- Marketing wrote:
>> On 2013-01-19, at 4:57 AM, John Baldwin <jhb@freebsd.org> wrote:
>>> On Tuesday, December 18, 2012 11:58:36 PM Hub- Marketing wrote:
>>>> I'm running a few servers sitting on top of a NetAPP file server =85
>>>> everything runs great, but periodically I'm getting:
>>>>=20
>>>> nfs_getpages: error 13
>>>> vm_fault: pager read error, pid 11355 (https)
>>>=20
>>> Are you using interruptible mounts ("intr" mount option)?
>>=20
>> 192.168.1.253:/vol/vol1 /vm nfs rw,intr,soft,nolockd =
0 =20
>> 0
>>=20
>> I just added the 'soft' option to the mix =85 nolockd is enabled =
since I know
>> for a fact that its not possible for two processes to access the same =
file
>> on both mounts at the same time =85
>=20
> Ah, ok. I just fixed a bug with interruptible mounts in HEAD where =
having
> a signal interrupt an NFS request returns EACCESS (13) rather than =
EINTR.
> You should retest with that fix applied.
>=20
> --=20
> John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3AD6C5A-A263-4A9A-9485-D9CB8821C35A>