Thanks for testing Nathan, that is the expected behaviour it might be
nice if we had the concept of a sysctl which is at its auto value and
hence we could use that to determine if we should recalculate said
automatic values which hadn't been manually set but we don't have that
unfortunately.
I was just testing this a bit.
I can now set max in loader.conf as expected.
I did notice one thing that I thought was a bit strange though.
As a reference, here are my defaults without any ARC tunables/sysctls:
vfs.zfs.arc_meta_limit: 3903459328
vfs.zfs.arc_min: 1951729664
vfs.zfs.arc_max: 1561
On 06/07/2016 21:39, Eric van Gyzen wrote:
On 07/06/16 03:35 PM, Steven Hartland wrote:
The ARC settings and kmem aren't initialised when tunables are loaded
so the tests fail.
I've fixed this locally by blindly setting if ARC is not configured.
Request to commit the fix is with re@
In the mea
Awesome.
I'll probably try this tonight or tomorrow.
Thanks very much!
On Wed, Jul 6, 2016 at 4:35 PM, Steven Hartland
wrote:
> The ARC settings and kmem aren't initialised when tunables are loaded so
> the tests fail.
>
> I've fixed this locally by blindly setting if ARC is not configured.
> R
On 07/06/16 03:35 PM, Steven Hartland wrote:
> The ARC settings and kmem aren't initialised when tunables are loaded
> so the tests fail.
>
> I've fixed this locally by blindly setting if ARC is not configured.
> Request to commit the fix is with re@
>
> In the mean time the patch is attached.
>
>
The ARC settings and kmem aren't initialised when tunables are loaded so
the tests fail.
I've fixed this locally by blindly setting if ARC is not configured.
Request to commit the fix is with re@
In the mean time the patch is attached.
Thanks for the report and sorry about the breakage.
On
On 06/07/2016 02:25, Allan Jude wrote:
On 2016-07-05 20:27, Steven Hartland wrote:
Ahh right, let me check that.
On 06/07/2016 00:51, Nathan Bosley wrote:
I actually have this same problem.
I'll send more details when I get home later.
I think the problem started for me after r302265.
Before
Maybe I misunderstood after all.
I took this:
"You can work around it temporarily by setting a lower arc_min first."
To mean that I could do something like:
vfs.zfs.arc_min="1073741824"
vfs.zfs.arc_max="8589934592"
in loader.conf, which would circumvent the problem.
But with the above, in that or
OK, I follow you now.
Thanks for the explanation.
I will try that later tonight or tomorrow.
On Tue, Jul 5, 2016 at 9:45 PM, Allan Jude wrote:
> On 2016-07-05 21:32, Nathan Bosley wrote:
> > I think in about 4 - 5 hours I can show what values I'm using in
> > loader.conf under, say, r302264 and
On 2016-07-05 21:32, Nathan Bosley wrote:
> I think in about 4 - 5 hours I can show what values I'm using in
> loader.conf under, say, r302264 and r302265 for comparison. I'm not 100%
> sure that the problem arose for me in r302265; I merely suspect it.
>
> On Tue, Jul 5, 2016 at 9:25 PM, Allan Ju
I think in about 4 - 5 hours I can show what values I'm using in
loader.conf under, say, r302264 and r302265 for comparison. I'm not 100%
sure that the problem arose for me in r302265; I merely suspect it.
On Tue, Jul 5, 2016 at 9:25 PM, Allan Jude wrote:
> On 2016-07-05 20:27, Steven Hartland w
On 2016-07-05 20:27, Steven Hartland wrote:
> Ahh right, let me check that.
>
> On 06/07/2016 00:51, Nathan Bosley wrote:
>> I actually have this same problem.
>> I'll send more details when I get home later.
>>
>> I think the problem started for me after r302265.
>> Before that, I can set vfs.zfs
Ahh right, let me check that.
On 06/07/2016 00:51, Nathan Bosley wrote:
I actually have this same problem.
I'll send more details when I get home later.
I think the problem started for me after r302265.
Before that, I can set vfs.zfs.arc_max and vfs.zfs.arc_min in loader.conf.
After r302265, se
I actually have this same problem.
I'll send more details when I get home later.
I think the problem started for me after r302265.
Before that, I can set vfs.zfs.arc_max and vfs.zfs.arc_min in loader.conf.
After r302265, setting either vfs.zfs.arc_max or vfs.zfs.arc_min in
loader.conf results in t
What is it currently?
Just had a quick play here:
sysctl vfs.zfs.arc_max
vfs.zfs.arc_max: 32283127808
sysctl vfs.zfs.arc_max=32283127807
vfs.zfs.arc_max: 32283127808 -> 32283127807
sysctl vfs.zfs.arc_max=32283127808
vfs.zfs.arc_max: 32283127807 -> 32283127808
Error 22 = EINVAL so I suspect you'r
15 matches
Mail list logo
