On 21.03.2014, at 03:45, Rick Macklem wrote:
> Markus Gebert wrote:
>>
>> On 20.03.2014, at 14:51, woll...@bimajority.org wrote:
>>
>>> In article <21290.60558.750106.630...@hergotha.csail.mit.edu>, I
>>> wrote:
>>>
Since we put this server into production, random network system
cal
Markus Gebert wrote:
>
> On 20.03.2014, at 14:51, woll...@bimajority.org wrote:
>
> > In article <21290.60558.750106.630...@hergotha.csail.mit.edu>, I
> > wrote:
> >
> >> Since we put this server into production, random network system
> >> calls
> >> have started failing with [EFBIG] or maybe so
On 20.03.2014, at 14:51, woll...@bimajority.org wrote:
> In article <21290.60558.750106.630...@hergotha.csail.mit.edu>, I wrote:
>
>> Since we put this server into production, random network system calls
>> have started failing with [EFBIG] or maybe sometimes [EIO]. I've
>> observed this with a
In article <21290.60558.750106.630...@hergotha.csail.mit.edu>, I wrote:
>Since we put this server into production, random network system calls
>have started failing with [EFBIG] or maybe sometimes [EIO]. I've
>observed this with a simple ping, but various daemons also log the
>errors:
>Mar 20 09:
turn off TSO
the problems sound similar to the one I reported a while back. truing off tso
fixed it.
danny
On Mar 20, 2014, at 3:26 PM, Garrett Wollman wrote:
> I recently put a new server running 9.2 (with a local patches for NFS)
> into production, and it's immediately started to fail in an
I recently put a new server running 9.2 (with a local patches for NFS)
into production, and it's immediately started to fail in an odd way.
Since I pounded this server pretty heavily and never saw the error in
testing, I'm more than a little bit taken aback. We have identical
hardware in productio
