Date: Sat, 13 Jul 2013 18:39:28 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Filesystem wedges caused by r251446 Message-ID: <E1Uy2r2-0003r7-0x@clue.co.za> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Uy2r2-0003r7-0x>