Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Tags: Architectures Platforms default
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

Architectures Platforms default
Ryan Moeller
ZTS: Eliminate partitioning in zpool_import setup

There doesn't seem to be a need for this complexity.

Reviewed-by: John Kennedy <john.kennedy@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
Closes #9854
Ryan Moeller
ZTS: Make DVA pattern in zdb tests more robust

Ensure the capture ends at the first DVA in case there are multiple
DVAs on the same line by only capturing up to the first '>' character.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
Closes #9851
Brian Behlendorf
Unify target_cpu handling

Over the years several slightly different approaches were used
in the Makefiles to determine the target architecture.  This
change updates both the build system and Makefile to handle
this in a consistent fashion.

TARGET_CPU is set to i386, x86_64, powerpc, aarch6 or sparc64
and made available in the Makefiles to be used as appropriate.

Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #9848
Brian Behlendorf
ZTS: Enable zpool_create_008_pos.ksh

Remove the blkid version check from zpool_create_008_pos.ksh
so the test case will not be skipped.

All versions of blkid tested by the CI are either new enough
to not suffer from this issue, or have been patched as is
the case with CentOS 7 (libblkid-2.23.2-61).

Additionally, add a block_device_wait after device partitioning
to ensure the expected partitions will exist.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #9853
Ryan Moeller
ZTS: Eliminate partitioning in zpool_import setup

There doesn't seem to be a need for this complexity.

Signed-off-by: Ryan Moeller <ryan@ixsystems.com>

Pull-request: #9854 part 1/1
Ryan Moeller
ZTS: Fix incorrect is_physical_device usage

This check isn't meant to be used for command substitution.

Reviewed-by: John Kennedy <john.kennedy@delphix.com>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Ryan Moeller <ryan@ixsystems.com>
Closes #9844
Brian Behlendorf
ZTS: Enable zpool_create_008_pos.ksh

Remove the blkid version check from zpool_create_008_pos.ksh
so the test case will not be skipped.

All versions of blkid tested by the CI are either new enough
to not suffer from this issue, or have been patched as is
the case with CentOS 7 (libblkid-2.23.2-61).

Additionally, add a block_device_wait after device partitioning
to ensure the expected partitions will exist.

TEST_ZFSTESTS_TAGS="zpool_create"
TEST_ZFSTESTS_ITERS="25"

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>

Pull-request: #9853 part 1/1
Garrett Fields
attempt to fix build.... configure.ac addition

Pull-request: #9852 part 2/2
Garrett Fields
Auto-unlock ZFS native encrypted root filesystem using TPM2-tools v4.x

Signed-off-by: Garrett Fields <ghfields@gmail.com>

Pull-request: #9852 part 1/1
Ned Bass
zdb: add support for object ranges for zdb -d

Allow a range of object identifiers to dump with -d. This may
be useful when dumping a large dataset and you want to break
it up into multiple phases, or to resume where a previous scan
left off. Object type selection flags are supported to reduce
the performance overhead of verbosely dumping unwanted objects,
and to reduce the amount of post-processing work needed to
filter out unwanted objects from zdb output.

This change extends existing syntax in a backward-compatible
way. That is, the base case of a range is to specify a single
object identifier to dump. Ranges and object identifiers can
be intermixed as command line parameters.

Usage synopsis:

    Object ranges take the form <start>:<end>[:<flags>]
        start    Starting object number
        end      Ending object number, or -1 for no upper bound
        flags    Optional flags to select object types:
        A    All objects (this is the default)
        d    ZFS directories
        f    ZFS files
        m    SPA space maps
        z    ZAPs
        -    Negate effect of next flag

Examples:

# Dump all file objects
zdb -dd tank/fish 0:-1:f

# Dump all file and directory objects
zdb -dd tank/fish 0:-1:fd

# Dump all types except file and directory objects
zdb -dd tank/fish 0:-1:A-f-d

# Dump object IDs in a specific range
zdb -dd tank/fish 1000:2000

Signed-off-by: Ned Bass <bass6@llnl.gov>

Pull-request: #9832 part 1/1
Ned Bass
zdb: add support for object ranges for zdb -d

Allow a range of object identifiers to dump with -d. This may
be useful when dumping a large dataset and you want to break
it up into multiple phases, or to resume where a previous scan
left off. Object type selection flags are supported to reduce
the performance overhead of verbosely dumping unwanted objects,
and to reduce the amount of post-processing work needed to
filter out unwanted objects from zdb output.

This change extends existing syntax in a backward-compatible
way. That is, the base case of a range is to specify a single
object identifier to dump. Ranges and object identifiers can
be intermixed as command line parameters.

Usage synopsis:

    Object ranges take the form <start>:<end>[:<flags>]
        start    Starting object number
        end      Ending object number, or -1 for no upper bound
        flags    Optional flags to select object types:
        A    All objects (this is the default)
        d    ZFS directories
        f    ZFS files
        m    SPA space maps
        z    ZAPs
        -    Negate effect of next flag

Examples:

# Dump all file objects
zdb -dd tank/fish 0:-1:f

# Dump all file and directory objects
zdb -dd tank/fish 0:-1:fd

# Dump all types except file and directory objects
zdb -dd tank/fish 0:-1:A-f-d

# Dump object IDs in a specific range
zdb -dd tank/fish 1000:2000

Signed-off-by: Ned Bass <bass6@llnl.gov>

Pull-request: #9832 part 1/1
  • Amazon 2 x86_64 (BUILD): cloning zfs -  stdio
  • Debian 8 arm (BUILD): cloning zfs -  stdio
  • Debian 8 ppc (BUILD): cloning zfs -  stdio
  • Kernel.org Built-in x86_64 (BUILD): cloning zfs -  stdio
  • Ubuntu 18.04 x86_64 (STYLE): cloning zfs -  stdio
George Amanakis
Trim L2ARC

Teach l2arc_evict() to trim the L2ARC before evicting headers from it by
introducing a public vdev_trim_simple() wrapper.

Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9789 part 1/1
Attila Fülöp
Use avx as the fastest implementaion.

Signed-off-by: Attila Fülöp <attila@fueloep.org>

Pull-request: #9749 part 7/7
Attila Fülöp
Always clear FPU registers

Signed-off-by: Attila Fülöp <attila@fueloep.org>
Requires-builders: style

Pull-request: #9749 part 6/6
Attila Fülöp
fix MOVBE push from wrong worktree

Signed-off-by: Attila Fülöp <attila@fueloep.org>

Pull-request: #9749 part 5/5
Attila Fülöp
Assert against issue #9661

Signed-off-by: Attila Fülöp <attila@fueloep.org>

Pull-request: #9749 part 4/5
Attila Fülöp
Add third party licenses

Signed-off-by: Attila Fülöp <attila@fueloep.org>
Requires-builders: none

Pull-request: #9749 part 3/5
Attila Fülöp
fix crash while switching to avx impl

Signed-off-by: Attila Fülöp <attila@fueloep.org>

Pull-request: #9749 part 2/5
Attila Fülöp
ICP: Improve AES-GCM performance

Currently SIMD accelerated AES-GCM performance is limited by two
factors:

a. The need to disable preemption and interrupts and save the FPU
state before using it and to do the reverse when done. Due to the
way the code is organized (see (b) below) we have to pay this price
twice for each 16 byte GCM block processed.

b. Most processing is done in C, operating on single GCM blocks.
The use of SIMD instructions is limited to the AES encryption of the
counter block (AES-NI) and the Galois multiplication (PCLMULQDQ).
This leads to the FPU not being fully utilized for crypto
operations.

To solve (a) we do crypto processing in larger chunks while owning
the FPU. An `icp_gcm_avx_chunk_size` module parameter was introduced
to make this chunk size tweakable. It defaults to 32 KiB. This step
alone roughly doubles performance. (b) is tackled by porting and
using the highly optimized openssl AES-GCM assembler routines, which
do all the processing (CTR, AES, GMULT) in a single routine. Both
steps together result in up to 32x reduction of the time spend in
the en/decryption routines, leading up to approximately 12x
throughput increase for large (128 KiB) blocks.

Signed-off-by: Attila Fülöp <attila@fueloep.org>

Pull-request: #9749 part 1/5
Paul Zuchowski
Fix zdb -R with 'b' flag

zdb -R :b fails due to the indirect block being compressed,
and the 'b' and 'd' flag not working in tandem when specified.
Fix the flag parsing code and create a zfs test for zdb -R
block display.  Also fix the zio flags where the dotted notation
for the vdev portion of DVA (i.e. 0.0:offset:length) fails.

Signed-off-by: Paul Zuchowski <pzuchowski@datto.com>
Fixes #9640

Pull-request: #9729 part 3/3
Paul Zuchowski
zdb -d should accept the numeric objset id

As an alternative to the dataset name, zdb now allows the decimal
or hexadecimal objset ID to be specified.  When permanent errors
are reported as 2 hexadecimal numbers (objset ID : object ID) in
zpool status; you can now use 'zdb <pool>[/objset ID] object' to
determine the names of the objset and object which have the error.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Signed-off-by: Paul Zuchowski <pzuchowski@datto.com>
Closes #9733

Pull-request: #9729 part 2/3
Paul Zuchowski
Fix zdb -R with 'b' flag

zdb -R :b fails due to the indirect block being compressed,
and the 'b' and 'd' flag not working in tandem when specified.
Fix the flag parsing code and create a zfs test for zdb -R
block display.  Also fix the zio flags where the dotted notation
for the vdev portion of DVA (i.e. 0.0:offset:length) fails.

Signed-off-by: Paul Zuchowski <pzuchowski@datto.com>
Fixes #9640

Pull-request: #9729 part 1/3
InsanePrawn
Systemd mount generator: Generate noauto units; add control properties

This commit refactors the systemd mount generators and makes the
following major changes:

- The generator now generates units for datasets marked canmount=noauto,
  too. These units are NOT WantedBy local-fs.target.
  If there are multiple noauto datasets for a path, no noauto unit will
  be created. Datasets with canmount=on are prioritized.

- Introduces handling of new user properties which are now included in
  the zfs-list.cache files:
    - org.open-zfs.systemd:noauto:
      Disables symlinking into and ordering before local-fs.target.
    - org.open-zfs.systemd:requires:
      List of units to require for this mount unit
    - org.open-zfs.systemd:requires-mounts-for:
      List of mounts to require by this mount unit
    - org.open-zfs.systemd:before:
      List of units to order after this mount unit
    - org.open-zfs.systemd:after:
      List of units to order before this mount unit
    - org.open-zfs.systemd:wanted-by:
      List of units to add a Wants dependency on this mount unit to
      (local-fs.target by default)
    - org.open-zfs.systemd:required-by:
      List of units to add a Requires dependency on this mount unit to
    - org.open-zfs.systemd:nofail:
      Toggles between a wants and a requires dependency.
    - org.open-zfs.systemd:ignore:
      Do not generate a mount unit for this dataset.

  Consult the updated man page for detailed documentation.

- Restructures and extends the zfs-mount-generator(8) man page with the
  above properties, information on unit ordering and a license header.

- Changes the output directory of the generator when run without
  arguments for debug purposes from /tmp to /tmp/zfs-mount-generator

Signed-off-by: InsanePrawn <insane.prawny@gmail.com>

Pull-request: #9649 part 2/2
InsanePrawn
Systemd mount generator: Silence shellcheck warnings

Silences a warning about an intentionally unquoted variable.
Fixes a warning caused by strings split across lines by slightly
refactoring keyloadcmd.

Signed-off-by: InsanePrawn <insane.prawny@gmail.com>

Pull-request: #9649 part 1/2
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Refactor mutex in l2arc_spa_rebuild_start and l2arc_remove_vdev

Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 2/2
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
George Amanakis
Persistent L2ARC

This commit makes the L2ARC persistent across reboots. It is largely
based on issue 3525 in Illumos.

Co-authored-by: Saso Kiselkov <skiselkov@gmail.com>
Co-authored-by: Jorgen Lundman <lundman@lundman.net>
Co-authored-by: George Amanakis <gamanakis@gmail.com>
Ported-by: Yuxuan Shui <yshuiv7@gmail.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>

Pull-request: #9582 part 1/1
  • Kernel.org Built-in x86_64 (BUILD): cloning zfs -  stdio
  • Ubuntu 18.04 x86_64 (STYLE): cloning zfs -  stdio
Christian Schwarz
zcp: add zfs.sync.bookmark

supports bookmark creation and cloning

Signed-off-by: Christian Schwarz <me@cschwarz.com>

Pull-request: #9571 part 8/8
Christian Schwarz
zcp: add zfs.sync.bookmark

supports bookmark creation and cloning

Signed-off-by: Christian Schwarz <me@cschwarz.com>

Pull-request: #9571 part 8/8
Christian Schwarz
zcp: add zfs.sync.bookmark

supports bookmark creation and cloning

Signed-off-by: Christian Schwarz <me@cschwarz.com>

Pull-request: #9571 part 7/7
Christian Schwarz
zcp: add zfs.sync.bookmark

supports bookmark creation and cloning

Signed-off-by: Christian Schwarz <me@cschwarz.com>

Pull-request: #9571 part 7/7
Christian Schwarz
zcp: add zfs.sync.bookmark

supports bookmark creation and cloning

Signed-off-by: Christian Schwarz <me@cschwarz.com>

Pull-request: #9571 part 7/7