Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Walter Haidinger
Am 30.03.2011 21:54, schrieb Claudio Jeker: > I guess there is a reason why the default is 8k. Shouldn't mount_nfs(8) be updated then? It still says: -r readsize Set the read data size to the specified value. It should normally be a power of 2 greater than or equal to 1024. No recommendation f

horribly slow fsck_ffs pass1 performance

2011-03-30 Thread Amit Kulkarni
Hi, In fsck_ffs's pass1.c it just takes forever for large sized partitions and also if you have very high number of files stored on that partition (used inodes count goes high). fsck main limitation is in pass1.c. In pass1.c I found out that it in fact proceeded to check all inodes, but there's

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Bret S. Lambert
On Wed, Mar 30, 2011 at 09:54:45PM +0200, Claudio Jeker wrote: > On Wed, Mar 30, 2011 at 08:36:45PM +0200, Walter Haidinger wrote: > > Am 30.03.2011 15:23, schrieb Claudio Jeker: > > > Buffers below 8k are stupid. For TCP just use 32k or even 64k. 512byte > > > buffers are silly. They get internall

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Claudio Jeker
On Wed, Mar 30, 2011 at 08:36:45PM +0200, Walter Haidinger wrote: > Am 30.03.2011 15:23, schrieb Claudio Jeker: > > Buffers below 8k are stupid. For TCP just use 32k or even 64k. 512byte > > buffers are silly. They get internally rounded up since the smallest > > packet seems to be 512bytes data pl

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Claudio Jeker
On Wed, Mar 30, 2011 at 08:34:24PM +0200, Mark Kettenis wrote: > > Date: Tue, 29 Mar 2011 22:42:47 +0200 > > From: Claudio Jeker > > > > Here is a possible fix. The problem was that because of the way NFS uses > > the socket API it did not turn of the sendbuffer scaling which reset the > > size o

Olde Fort Inn, Google First Page Guaranteed?

2011-03-30 Thread Russell Chen
Having trouble reading this email? View it in your browser. [http://bm1.nocserv2.com/display.php?M=721973&C=b76c0fb6bb811a57db4d70a488f5bf04&S=123&L=29&N=30] Google First Page Guaranteed? We can get your business Olde Fort Inn on 1st page of Google Before You're Billed! We Ensure You Receive C

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Walter Haidinger
Am 30.03.2011 15:23, schrieb Claudio Jeker: > Buffers below 8k are stupid. For TCP just use 32k or even 64k. 512byte > buffers are silly. They get internally rounded up since the smallest > packet seems to be 512bytes data plus header. This will give you TCP send > and recv buffers of around 1200by

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Mark Kettenis
> Date: Tue, 29 Mar 2011 22:42:47 +0200 > From: Claudio Jeker > > Here is a possible fix. The problem was that because of the way NFS uses > the socket API it did not turn of the sendbuffer scaling which reset the > size of the socket back to 17376 bytes which is a no go when a buffer of > more t

Iluminación LED y Solar

2011-03-30 Thread TBX
$200 PesosFaroles solares demarcadores x 4 unidades Practica Estaca Solar Led / incluye 4 Estacas / Estaca para clavar en la tierra / Ideal para decoración de jard

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Claudio Jeker
On Wed, Mar 30, 2011 at 03:07:13PM +0200, Walter Haidinger wrote: > Am 29.03.2011 22:42, schrieb Claudio Jeker: > > Here is a possible fix. The problem was that because of the way NFS uses > > the socket API it did not turn of the sendbuffer scaling which reset the > > size of the socket back to 17

Re: NFS writes lock up system with -o tcp,-w32768

2011-03-30 Thread Walter Haidinger
Am 29.03.2011 22:42, schrieb Claudio Jeker: > Here is a possible fix. The problem was that because of the way NFS uses > the socket API it did not turn of the sendbuffer scaling which reset the > size of the socket back to 17376 bytes which is a no go when a buffer of > more then 17k is generated b