From owner-freebsd-current@FreeBSD.ORG  Sat Jul 13 16:39:36 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 729A77B2;
 Sat, 13 Jul 2013 16:39:36 +0000 (UTC) (envelope-from ianf@clue.co.za)
Received: from zcs03.jnb1.cloudseed.co.za (zcs03.jnb1.cloudseed.co.za
 [41.154.0.139]) by mx1.freebsd.org (Postfix) with ESMTP id 0DA8F18B5;
 Sat, 13 Jul 2013 16:39:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTP id 925B52B43283;
 Sat, 13 Jul 2013 18:39:32 +0200 (SAST)
X-Virus-Scanned: amavisd-new at zcs03.jnb1.cloudseed.co.za
Received: from zcs03.jnb1.cloudseed.co.za ([127.0.0.1])
 by localhost (zcs03.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id x2ThyXa+wBmu; Sat, 13 Jul 2013 18:39:30 +0200 (SAST)
Received: from clue.co.za (unknown [41.154.88.19])
 by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id 940F42B43262;
 Sat, 13 Jul 2013 18:39:30 +0200 (SAST)
Received: from localhost ([127.0.0.1] helo=zen)
 by clue.co.za with esmtp (Exim 4.80.1 (FreeBSD))
 (envelope-from <ianf@clue.co.za>)
 id 1Uy2r2-0003r7-0x; Sat, 13 Jul 2013 18:39:28 +0200
To: Konstantin Belousov <kostikbel@gmail.com>
From: Ian FREISLICH <ianf@clue.co.za>
Subject: Re: Filesystem wedges caused by r251446
In-Reply-To: <20130713100337.GK91021@kib.kiev.ua>
References: <20130713100337.GK91021@kib.kiev.ua>
 <20130713054220.GJ91021@kib.kiev.ua> <20130712201051.GI91021@kib.kiev.ua>
 <201307110923.06548.jhb@freebsd.org> <201307091202.24493.jhb@freebsd.org>
 <E1UufRq-0001sg-HG@clue.co.za> <E1UxEWB-0000il-21@clue.co.za>
 <E1Uxhoe-0000d9-Sc@clue.co.za> <E1Uxkyo-0002mE-MJ@clue.co.za>
 <E1Uxuy4-0003KB-OZ@clue.co.za>
X-Attribution: BOFH
Date: Sat, 13 Jul 2013 18:39:28 +0200
Message-Id: <E1Uy2r2-0003r7-0x@clue.co.za>
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jul 2013 16:39:36 -0000

Konstantin Belousov wrote:
> > Yes.  This state of affairs doesn't happen on r251445 and further
> > testing on my side shows it doesn't hapen on all my amd64 servers.
> > It appears that this particular server type (Dell R200) running
> > amd64 with geom_mirror is affected.  I will have to test further
> > by destroying the mirror and removing it from the kernel and see
> > if I can still reproduce the issue.  Perhaps r251446 exposes
> > insufficient locking on opperations affecting these variables.
> No.  The lorunningspace is constant for the system lifetime.
> It can only be changed by the sysctl vfs.lorunningspace.
> Look into /etc/sysctl.conf or scripts which apply sysctl settings.

Wipes egg from face.

/etc/sysctl.conf:

vfs.hirunningspace=4194304

So, then did r251446 actually start using this value or did other
values get significantly tuned up?  I recall now setting this nearly
a year ago when we did our ZFS tuning and it was a four fold increase
on the defaults.

Sorry for the noise.

Ian

-- 
Ian Freislich