Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Dec 2015 09:02:03 -0700
From:      Alan Somers <asomers@freebsd.org>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        "src-committers@freebsd.org" <src-committers@freebsd.org>, svn-src-projects@freebsd.org
Subject:   Re: svn commit: r292353 - projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_set
Message-ID:  <CAOtMX2gk%2BhhPrg-9Zva%2BSCLVLHu%2BykJmNPhZvJu8H6-N3vVBng@mail.gmail.com>
In-Reply-To: <5671E0AA.1020102@FreeBSD.org>
References:  <201512161930.tBGJUiTn047536@repo.freebsd.org> <5671E0AA.1020102@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 16, 2015 at 3:07 PM, Andriy Gapon <avg@freebsd.org> wrote:
> On 16/12/2015 21:30, Alan Somers wrote:
>> Author: asomers
>> Date: Wed Dec 16 19:30:44 2015
>> New Revision: 292353
>> URL: https://svnweb.freebsd.org/changeset/base/292353
>>
>> Log:
>>   Disable read-only testing of space usage properties.
>>
>>   These properties (used, available, referenced) are easily influenced by
>>   internal machinations in ZFS, and currently cause random failures of this
>>   test when run on a system running the BP workers.
>>
>>   The test itself checks that the properties can't be changed, and goes
>>   farther than just asserting that the 'zfs set' command fails: it also checks
>>   that the property's value still matches its original value.
>>
>>   For some reason, however, background activity causes short-term changes in
>>   these values, that appear not to involve either an ioctl (at least one that
>>   would show up in 'zpool history') or filesystem accesses.  This is hopefully
>>   still only temporary just to get the tests passing.
>>
>>   Submitted by:       Will
>>   Sponsored by:       Spectra Logic Corp
>
> FWIW,
> hhttps://github.com/avg-I/openzfs/commit/e7a8782eb9ea84e6db92891dfd5a74c655d0a44a
> The change is a bit lame, but better than nothing.
>

Interesting.  We had no idea that's what was causing those properties
to change.  We thought it must be the result of some unknown
background process.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gk%2BhhPrg-9Zva%2BSCLVLHu%2BykJmNPhZvJu8H6-N3vVBng>