Describe how unaccounted changes are detected without Star Trek references, for

everyone in 2018.

Thanks to maya & gdt
This commit is contained in:
sevan 2018-12-10 03:58:30 +00:00
parent 98ec1b8df8
commit a8174c34c4

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ztest.1,v 1.3 2018/12/08 14:55:53 sevan Exp $
.\" $NetBSD: ztest.1,v 1.4 2018/12/10 03:58:30 sevan Exp $
.\"
.\" Copyright (c) 2018 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -27,7 +27,7 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"/
.Dd December 8, 2018
.Dd December 10, 2018
.Dt ZTEST 1
.Os
.Sh NAME
@ -75,6 +75,15 @@ To verify that the on-disk consistency is never lost after a crash, child
processes are killed at random with a SIGKILL signal, after which the parent
process invokes a new child to run the test again on the same storage pool.
.Pp
Many of the tests record the transaction group number as part of their data.
When reading old data, tests verify that the transaction group number is less
than the current, open state, transaction group to ensure the consistency of
tests and detect unaccounted changes.
It is advised that any new tests added to
.Nm
should also perform the same check with transaction group numbers, if
applicable.
.Pp
The main
.Nm
process uses an