2010-08-26 18:22:58 +00:00
|
|
|
/*
|
2022-04-09 12:37:22 +00:00
|
|
|
* This file is part of OpenZFS.
|
2010-08-26 18:22:58 +00:00
|
|
|
*
|
|
|
|
|
* Copyright (c) 2009 Lawrence Livermore National Security, LLC.
|
|
|
|
|
* Produced at Lawrence Livermore National Laboratory
|
|
|
|
|
* Written by:
|
|
|
|
|
* Brian Behlendorf <behlendorf1@llnl.gov>,
|
|
|
|
|
* Herb Wartens <wartens2@llnl.gov>,
|
|
|
|
|
* Jim Garlick <garlick@llnl.gov>
|
|
|
|
|
* LLNL-CODE-403049
|
|
|
|
|
*
|
|
|
|
|
* CDDL HEADER START
|
|
|
|
|
*
|
|
|
|
|
* The contents of this file are subject to the terms of the
|
|
|
|
|
* Common Development and Distribution License, Version 1.0 only
|
|
|
|
|
* (the "License"). You may not use this file except in compliance
|
|
|
|
|
* with the License.
|
|
|
|
|
*
|
|
|
|
|
* You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
|
|
|
|
|
* or http://www.opensolaris.org/os/licensing.
|
|
|
|
|
* See the License for the specific language governing permissions
|
|
|
|
|
* and limitations under the License.
|
|
|
|
|
*
|
|
|
|
|
* When distributing Covered Code, include this CDDL HEADER in each
|
|
|
|
|
* file and include the License file at usr/src/OPENSOLARIS.LICENSE.
|
|
|
|
|
* If applicable, add the following below this CDDL HEADER, with the
|
|
|
|
|
* fields enclosed by brackets "[]" replaced with your own identifying
|
|
|
|
|
* information: Portions Copyright [yyyy] [name of copyright owner]
|
|
|
|
|
*
|
|
|
|
|
* CDDL HEADER END
|
|
|
|
|
*/
|
|
|
|
|
|
2022-04-07 23:07:08 +00:00
|
|
|
AC_INIT(m4_esyscmd(awk '/^Name:/ {printf $2}' META),
|
|
|
|
|
m4_esyscmd(awk '/^Version:/ {printf $2}' META))
|
2010-08-26 18:22:58 +00:00
|
|
|
AC_LANG(C)
|
|
|
|
|
ZFS_AC_META
|
|
|
|
|
AC_CONFIG_AUX_DIR([config])
|
2013-03-30 02:33:09 +00:00
|
|
|
AC_CONFIG_MACRO_DIR([config])
|
2021-01-03 00:55:55 +00:00
|
|
|
AC_CANONICAL_TARGET
|
2010-08-26 18:22:58 +00:00
|
|
|
AM_MAINTAINER_MODE
|
2013-04-02 22:16:39 +00:00
|
|
|
m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
|
2022-04-07 23:07:08 +00:00
|
|
|
AM_INIT_AUTOMAKE([subdir-objects foreign])
|
2010-08-26 18:22:58 +00:00
|
|
|
AC_CONFIG_HEADERS([zfs_config.h], [
|
|
|
|
|
(mv zfs_config.h zfs_config.h.tmp &&
|
2010-09-04 20:26:23 +00:00
|
|
|
awk -f ${ac_srcdir}/config/config.awk zfs_config.h.tmp >zfs_config.h &&
|
2010-08-26 18:22:58 +00:00
|
|
|
rm zfs_config.h.tmp) || exit 1])
|
|
|
|
|
|
2021-01-03 00:55:55 +00:00
|
|
|
LT_INIT
|
2010-08-26 18:22:58 +00:00
|
|
|
AC_PROG_INSTALL
|
|
|
|
|
AC_PROG_CC
|
2021-05-08 13:04:48 +00:00
|
|
|
AC_PROG_LN_S
|
config: better libtirpc detection
Improve the autoconf code for finding libtirpc and do not assume the
headers are in /usr/include/tirpc.
Also remove this assumption from the `rpc/xdr.h` header in libspl and
use the same `#include_next` mechanism that is used for other libspl
headers.
Include pkg.m4 from pkg-config in config/ for PKG_CHECK_MODULES(), the
file license allows this.
Include ax_save_flags.m4 and ax_restore_flags.m4 from autoconf-archive,
the file licenses are compatible. Use the 2012 versions so as not rely
on a more recent autoconf feature AS_VAR_COPY(), which breaks some build
slaves.
Add new macro library `config/find_system_library.m4` which defines the
FIND_SYSTEM_LIBRARY() macro which is a convenience wrapper over using
PKG_CHECK_MODULES() with a fallback to standard library locations and
some sanity checks.
The parameters are:
```
FIND_SYSTEM_LIBRARY(VARIABLE-PREFIX, MODULE, HEADER, HEADER-PREFIXES,
LIBRARY, FUNCTIONS, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
```
`HEADER-PREFIXES` and `FUNCTIONS` are comma-separated m4 lists.
For libtirpc we are using:
```
FIND_SYSTEM_LIBRARY(LIBTIRPC, [libtirpc], [rpc/xdr.h], [tirpc], [tirpc],
[xdrmem_create], [], [...])
```
The headers are first checked for without the prefixes and then with.
This system works with pkg-config and falls back on checking standard
header/library locations, it can be easily overridden by the user by
setting the `PREFIX_CFLAGS` and `PREFIX_LIBS` variables which are
automatically added to the `./configure --help` output.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rafael Kitover <rkitover@gmail.com>
Closes #7422
Closes #8313
2019-03-03 00:19:05 +00:00
|
|
|
PKG_PROG_PKG_CONFIG
|
2010-08-26 18:22:58 +00:00
|
|
|
AM_PROG_AS
|
2016-06-15 22:47:05 +00:00
|
|
|
AM_PROG_CC_C_O
|
2017-09-23 01:49:57 +00:00
|
|
|
AX_CODE_COVERAGE
|
2018-08-15 16:52:28 +00:00
|
|
|
_AM_PROG_TAR(pax)
|
2010-08-26 18:22:58 +00:00
|
|
|
|
|
|
|
|
ZFS_AC_LICENSE
|
|
|
|
|
ZFS_AC_CONFIG
|
2020-07-01 16:05:21 +00:00
|
|
|
ZFS_AC_PACKAGE
|
2010-08-26 18:22:58 +00:00
|
|
|
ZFS_AC_DEBUG
|
2014-09-23 18:29:30 +00:00
|
|
|
ZFS_AC_DEBUGINFO
|
2018-02-16 01:53:18 +00:00
|
|
|
ZFS_AC_DEBUG_KMEM
|
|
|
|
|
ZFS_AC_DEBUG_KMEM_TRACKING
|
2021-03-05 20:16:41 +00:00
|
|
|
ZFS_AC_DEBUG_INVARIANTS
|
2010-08-26 18:22:58 +00:00
|
|
|
|
2015-07-01 22:23:09 +00:00
|
|
|
AC_CONFIG_FILES([
|
2010-08-26 18:22:58 +00:00
|
|
|
Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
contrib/Makefile
|
|
|
|
|
contrib/bash_completion.d/Makefile
|
Add tracepoints for taskq entry lifetime events
This adds some new DTRACE_PROBE* endpoints so that we can observe taskq
latencies on a system. Additionally, a new "taskqlatency.bt" script is
added to do this observation via "bpftrace". Lastly, a "zfs-trace.sh"
script is added to wrap "bpftrace" with the proper options required to
run and use "taskqlatency.bt".
For example, with these changes in place, a user can run the following:
$ cd ./contrib/bpftrace
$ sudo ./zfs-trace.sh taskqlatency.bt
Attaching 6 probes...
^C
Here's some example output, showing latency information for time spent
executing the taskq entry's function:
@exec_lat_us[dp_sync_taskq, userquota_updates_task]:
[2, 4) 5 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[4, 8) 0 | |
[8, 16) 1 |@@@@@@@@@@ |
[16, 32) 2 |@@@@@@@@@@@@@@@@@@@@ |
@exec_lat_us[z_wr_int_h, zio_execute]:
[8, 16) 16 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[16, 32) 2 |@@@@@@ |
@exec_lat_us[z_wr_iss_h, zio_execute]:
[16, 32) 4 |@@@@@@@@@@@@@@@@ |
[32, 64) 13 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[64, 128) 1 |@@@@ |
@exec_lat_us[z_ioctl_int, zio_execute]:
[2, 4) 1 |@@@@ |
[4, 8) 11 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[8, 16) 8 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
@exec_lat_us[dp_sync_taskq, sync_dnodes_task]:
[2, 4) 1 |@@@@@@ |
[4, 8) 7 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[8, 16) 8 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[16, 32) 2 |@@@@@@@@@@@@@ |
[32, 64) 4 |@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[64, 128) 1 |@@@@@@ |
[128, 256) 0 | |
[256, 512) 1 |@@@@@@
Here's some example output, showing latency information for time spent
waiting on the taskq, prior to starting execution of entry's function:
@queue_lat_us[dp_sync_taskq]:
[2, 4) 1 |@@@@ |
[4, 8) 7 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[8, 16) 2 |@@@@@@@@ |
[16, 32) 3 |@@@@@@@@@@@@@ |
[32, 64) 12 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[64, 128) 6 |@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[128, 256) 0 | |
[256, 512) 1 |@@@@ |
@queue_lat_us[z_wr_iss]:
[4, 8) 4 |@@@@ |
[8, 16) 13 |@@@@@@@@@@@@@@@ |
[16, 32) 6 |@@@@@@@ |
[32, 64) 2 |@@ |
[64, 128) 12 |@@@@@@@@@@@@@@ |
[128, 256) 15 |@@@@@@@@@@@@@@@@@@ |
[256, 512) 33 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[512, 1K) 27 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[1K, 2K) 7 |@@@@@@@@ |
[2K, 4K) 14 |@@@@@@@@@@@@@@@@ |
[4K, 8K) 14 |@@@@@@@@@@@@@@@@ |
[8K, 16K) 23 |@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[16K, 32K) 43 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
@queue_lat_us[z_wr_int]:
[2, 4) 10 |@@@@@ |
[4, 8) 71 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[8, 16) 88 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[16, 32) 50 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[32, 64) 65 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[64, 128) 43 |@@@@@@@@@@@@@@@@@@@@@@@@@ |
[128, 256) 19 |@@@@@@@@@@@ |
[256, 512) 3 |@ |
[512, 1K) 1 | |
Reviewed by: Brad Lewis <brad.lewis@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Prakash Surya <prakash.surya@delphix.com>
Closes #9525
2019-10-24 21:13:41 +00:00
|
|
|
contrib/bpftrace/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
contrib/dracut/02zfsexpandknowledge/Makefile
|
|
|
|
|
contrib/dracut/90zfs/Makefile
|
|
|
|
|
contrib/dracut/Makefile
|
|
|
|
|
contrib/initramfs/Makefile
|
2020-05-02 23:46:46 +00:00
|
|
|
contrib/initramfs/conf.d/Makefile
|
|
|
|
|
contrib/initramfs/conf-hooks.d/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
contrib/initramfs/hooks/Makefile
|
|
|
|
|
contrib/initramfs/scripts/Makefile
|
|
|
|
|
contrib/initramfs/scripts/local-top/Makefile
|
2020-06-25 01:45:44 +00:00
|
|
|
contrib/pam_zfs_key/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
contrib/pyzfs/Makefile
|
|
|
|
|
contrib/pyzfs/setup.py
|
|
|
|
|
contrib/zcp/Makefile
|
2010-08-26 18:22:58 +00:00
|
|
|
etc/Makefile
|
2020-02-06 17:28:20 +00:00
|
|
|
etc/default/Makefile
|
2011-03-17 22:02:28 +00:00
|
|
|
etc/init.d/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
etc/modules-load.d/Makefile
|
|
|
|
|
etc/sudoers.d/Makefile
|
2014-01-19 14:36:49 +00:00
|
|
|
etc/systemd/Makefile
|
2018-04-06 21:11:09 +00:00
|
|
|
etc/systemd/system-generators/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
etc/systemd/system/Makefile
|
|
|
|
|
etc/zfs/Makefile
|
|
|
|
|
include/Makefile
|
2014-06-06 23:23:22 +00:00
|
|
|
lib/libzfs/libzfs.pc
|
2020-09-15 22:42:27 +00:00
|
|
|
lib/libzfsbootenv/libzfsbootenv.pc
|
Clean up lib dependencies
libzutil is currently statically linked into libzfs, libzfs_core and
libzpool. Avoid the unnecessary duplication by removing it from libzfs
and libzpool, and adding libzfs_core to libzpool.
Remove a few unnecessary dependencies:
- libuutil from libzfs_core
- libtirpc from libspl
- keep only libcrypto in libzfs, as we don't use any functions from
libssl
- librt is only used for clock_gettime, however on modern systems that's
in libc rather than librt. Add a configure check to see if we actually
need librt
- libdl from raidz_test
Add a few missing dependencies:
- zlib to libefi and libzfs
- libuuid to zpool, and libuuid and libudev to zed
- libnvpair uses assertions, so add assert.c to provide aok and
libspl_assertf
Sort the LDADD for programs so that libraries that satisfy dependencies
come at the end rather than the beginning of the linker command line.
Revamp the configure tests for libaries to use FIND_SYSTEM_LIBRARY
instead. This can take advantage of pkg-config, and it also avoids
polluting LIBS.
List all the required dependencies in the pkgconfig files, and move the
one for libzfs_core into the latter's directory. Install pkgconfig files
in $(libdir)/pkgconfig on linux and $(prefix)/libdata/pkgconfig on
FreeBSD, instead of /usr/share/pkgconfig, as the more correct location
for library .pc files.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
Closes #10538
2020-06-30 17:10:41 +00:00
|
|
|
lib/libzfs_core/libzfs_core.pc
|
2019-10-09 17:54:22 +00:00
|
|
|
man/Makefile
|
Cleanup linux module kbuild files
The linux module can be built either as an external module, or compiled
into the kernel, using copy-builtin. The source and build directories
are slightly different between the two cases, and currently, compiling
into the kernel still refers to some files from the configured ZFS
source tree, instead of the copies inside the kernel source tree. There
is also duplication between copy-builtin, which creates a Kbuild file to
build ZFS inside the kernel tree, and the top-level module/Makefile.in.
Fix this by moving the list of modules and the CFLAGS settings into a
new module/Kbuild.in, which will be used by the kernel kbuild
infrastructure, and using KBUILD_EXTMOD to distinguish the two cases
within the Makefiles, in order to choose appropriate include
directories etc.
Module CFLAGS setting is simplified by using subdir-ccflags-y (available
since 2.6.30) to set them in the top-level Kbuild instead of each
individual module. The disabling of -Wunused-but-set-variable is removed
from the lua and zfs modules. The variable that the Makefile uses is
actually not defined, so this has no effect; and the warning has long
been disabled by the kernel Makefile itself.
The target_cpu definition in module/{zfs,zcommon} is removed as it was
replaced by use of CONFIG_SPARC64 in
commit 70835c5b755e ("Unify target_cpu handling")
os/linux/{spl,zfs} are removed from obj-m, as they are not modules in
themselves, but are included by the Makefile in the spl and zfs module
directories. The vestigial Makefiles in os and os/linux are removed.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu>
Closes #10379
Closes #10421
2020-06-07 21:03:12 +00:00
|
|
|
module/Kbuild
|
2010-08-26 18:22:58 +00:00
|
|
|
module/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
rpm/Makefile
|
|
|
|
|
rpm/generic/Makefile
|
|
|
|
|
rpm/generic/zfs-dkms.spec
|
|
|
|
|
rpm/generic/zfs-kmod.spec
|
|
|
|
|
rpm/generic/zfs.spec
|
|
|
|
|
rpm/redhat/Makefile
|
|
|
|
|
rpm/redhat/zfs-dkms.spec
|
|
|
|
|
rpm/redhat/zfs-kmod.spec
|
|
|
|
|
rpm/redhat/zfs.spec
|
2010-08-26 18:22:58 +00:00
|
|
|
scripts/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/runfiles/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/test-runner/Makefile
|
Retire legacy test infrastructure
* Removed zpios kmod, utility, headers and man page.
* Removed unused scripts zpios-profile/*, zpios-test/*,
zpool-config/*, smb.sh, zpios-sanity.sh, zpios-survey.sh,
zpios.sh, and zpool-create.sh.
* Removed zfs-script-config.sh.in. When building 'make' generates
a common.sh with in-tree path information from the common.sh.in
template. This file and sourced by the test scripts and used
for in-tree testing, it is not included in the packages. When
building packages 'make install' uses the same template to
create a new common.sh which is appropriate for the packaging.
* Removed unused functions/variables from scripts/common.sh.in.
Only minimal path information and configuration environment
variables remain.
* Removed unused scripts from scripts/ directory.
* Remaining shell scripts in the scripts directory updated to
cleanly pass shellcheck and added to checked scripts.
* Renamed tests/test-runner/cmd/ to tests/test-runner/bin/ to
match install location name.
* Removed last traces of the --enable-debug-dmu-tx configure
options which was retired some time ago.
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #6509
2017-08-16 00:26:38 +00:00
|
|
|
tests/test-runner/bin/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/test-runner/include/Makefile
|
|
|
|
|
tests/test-runner/man/Makefile
|
|
|
|
|
tests/zfs-tests/Makefile
|
2017-04-12 20:36:48 +00:00
|
|
|
tests/zfs-tests/callbacks/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/cmd/Makefile
|
|
|
|
|
tests/zfs-tests/include/Makefile
|
|
|
|
|
tests/zfs-tests/tests/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/acl/Makefile
|
2021-03-16 22:00:14 +00:00
|
|
|
tests/zfs-tests/tests/functional/acl/off/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/acl/posix/Makefile
|
2020-10-09 16:27:14 +00:00
|
|
|
tests/zfs-tests/tests/functional/acl/posix-sa/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/alloc_class/Makefile
|
2018-01-29 18:24:52 +00:00
|
|
|
tests/zfs-tests/tests/functional/arc/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/atime/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/bootfs/Makefile
|
2019-12-19 19:53:55 +00:00
|
|
|
tests/zfs-tests/tests/functional/btree/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cache/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cachefile/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/casenorm/Makefile
|
2018-02-08 16:16:23 +00:00
|
|
|
tests/zfs-tests/tests/functional/channel_program/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/channel_program/lua_core/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/channel_program/synctask_core/Makefile
|
2016-12-16 23:15:48 +00:00
|
|
|
tests/zfs-tests/tests/functional/chattr/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/checksum/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/clean_mirror/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zdb/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs/Makefile
|
2017-09-25 17:32:34 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_bookmark/Makefile
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_change-key/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_clone/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_copies/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_create/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_destroy/Makefile
|
2017-09-28 20:04:14 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_diff/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_get/Makefile
|
2020-05-20 17:05:33 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_ids_to_path/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_inherit/Makefile
|
2020-08-01 15:44:54 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_jail/Makefile
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_load-key/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_mount/Makefile
|
2018-03-19 19:40:58 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_program/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_promote/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_property/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_receive/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_rename/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_reservation/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_rollback/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_send/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_set/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_share/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_snapshot/Makefile
|
2018-09-02 19:09:53 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_sysfs/Makefile
|
Native Encryption for ZFS on Linux
This change incorporates three major pieces:
The first change is a keystore that manages wrapping
and encryption keys for encrypted datasets. These
commands mostly involve manipulating the new
DSL Crypto Key ZAP Objects that live in the MOS. Each
encrypted dataset has its own DSL Crypto Key that is
protected with a user's key. This level of indirection
allows users to change their keys without re-encrypting
their entire datasets. The change implements the new
subcommands "zfs load-key", "zfs unload-key" and
"zfs change-key" which allow the user to manage their
encryption keys and settings. In addition, several new
flags and properties have been added to allow dataset
creation and to make mounting and unmounting more
convenient.
The second piece of this patch provides the ability to
encrypt, decyrpt, and authenticate protected datasets.
Each object set maintains a Merkel tree of Message
Authentication Codes that protect the lower layers,
similarly to how checksums are maintained. This part
impacts the zio layer, which handles the actual
encryption and generation of MACs, as well as the ARC
and DMU, which need to be able to handle encrypted
buffers and protected data.
The last addition is the ability to do raw, encrypted
sends and receives. The idea here is to send raw
encrypted and compressed data and receive it exactly
as is on a backup system. This means that the dataset
on the receiving system is protected using the same
user key that is in use on the sending side. By doing
so, datasets can be efficiently backed up to an
untrusted system without fear of data being
compromised.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Jorgen Lundman <lundman@lundman.net>
Signed-off-by: Tom Caputi <tcaputi@datto.com>
Closes #494
Closes #5769
2017-08-14 17:36:48 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_unload-key/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_unmount/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_unshare/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_upgrade/Makefile
|
2020-04-01 17:02:06 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_wait/Makefile
|
2021-11-11 19:26:18 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zhack/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_add/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_attach/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_clear/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_create/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_destroy/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_detach/Makefile
|
2017-10-26 23:49:33 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_events/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_expand/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_export/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_get/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_history/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_import/Makefile
|
2018-08-15 16:52:28 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_import/blockfiles/Makefile
|
OpenZFS 9102 - zfs should be able to initialize storage devices
PROBLEM
========
The first access to a block incurs a performance penalty on some platforms
(e.g. AWS's EBS, VMware VMDKs). Therefore we recommend that volumes are
"thick provisioned", where supported by the platform (VMware). This can
create a large delay in getting a new virtual machines up and running (or
adding storage to an existing Engine). If the thick provision step is
omitted, write performance will be suboptimal until all blocks on the LUN
have been written.
SOLUTION
=========
This feature introduces a way to 'initialize' the disks at install or in the
background to make sure we don't incur this first read penalty.
When an entire LUN is added to ZFS, we make all space available immediately,
and allow ZFS to find unallocated space and zero it out. This works with
concurrent writes to arbitrary offsets, ensuring that we don't zero out
something that has been (or is in the middle of being) written. This scheme
can also be applied to existing pools (affecting only free regions on the
vdev). Detailed design:
- new subcommand:zpool initialize [-cs] <pool> [<vdev> ...]
- start, suspend, or cancel initialization
- Creates new open-context thread for each vdev
- Thread iterates through all metaslabs in this vdev
- Each metaslab:
- select a metaslab
- load the metaslab
- mark the metaslab as being zeroed
- walk all free ranges within that metaslab and translate
them to ranges on the leaf vdev
- issue a "zeroing" I/O on the leaf vdev that corresponds to
a free range on the metaslab we're working on
- continue until all free ranges for this metaslab have been
"zeroed"
- reset/unmark the metaslab being zeroed
- if more metaslabs exist, then repeat above tasks.
- if no more metaslabs, then we're done.
- progress for the initialization is stored on-disk in the vdev’s
leaf zap object. The following information is stored:
- the last offset that has been initialized
- the state of the initialization process (i.e. active,
suspended, or canceled)
- the start time for the initialization
- progress is reported via the zpool status command and shows
information for each of the vdevs that are initializing
Porting notes:
- Added zfs_initialize_value module parameter to set the pattern
written by "zpool initialize".
- Added zfs_vdev_{initializing,removal}_{min,max}_active module options.
Authored by: George Wilson <george.wilson@delphix.com>
Reviewed by: John Wren Kennedy <john.kennedy@delphix.com>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed by: Pavel Zakharov <pavel.zakharov@delphix.com>
Reviewed by: Prakash Surya <prakash.surya@delphix.com>
Reviewed by: loli10K <ezomori.nozomu@gmail.com>
Reviewed by: Brian Behlendorf <behlendorf1@llnl.gov>
Approved by: Richard Lowe <richlowe@richlowe.net>
Signed-off-by: Tim Chase <tim@chase2k.com>
Ported-by: Tim Chase <tim@chase2k.com>
OpenZFS-issue: https://www.illumos.org/issues/9102
OpenZFS-commit: https://github.com/openzfs/openzfs/commit/c3963210eb
Closes #8230
2018-12-19 14:54:59 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_initialize/Makefile
|
2017-01-13 17:25:15 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_labelclear/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_offline/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_online/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_remove/Makefile
|
2017-10-26 19:26:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_reopen/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_replace/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_resilver/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_scrub/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_set/Makefile
|
2018-04-12 17:57:24 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_split/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_status/Makefile
|
2017-05-19 19:33:11 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_sync/Makefile
|
2019-03-29 16:13:20 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_trim/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_upgrade/Makefile
|
2018-08-15 16:52:28 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_upgrade/blockfiles/Makefile
|
Add subcommand to wait for background zfs activity to complete
Currently the best way to wait for the completion of a long-running
operation in a pool, like a scrub or device removal, is to poll 'zpool
status' and parse its output, which is neither efficient nor convenient.
This change adds a 'wait' subcommand to the zpool command. When invoked,
'zpool wait' will block until a specified type of background activity
completes. Currently, this subcommand can wait for any of the following:
- Scrubs or resilvers to complete
- Devices to initialized
- Devices to be replaced
- Devices to be removed
- Checkpoints to be discarded
- Background freeing to complete
For example, a scrub that is in progress could be waited for by running
zpool wait -t scrub <pool>
This also adds a -w flag to the attach, checkpoint, initialize, replace,
remove, and scrub subcommands. When used, this flag makes the operations
kicked off by these subcommands synchronous instead of asynchronous.
This functionality is implemented using a new ioctl. The type of
activity to wait for is provided as input to the ioctl, and the ioctl
blocks until all activity of that type has completed. An ioctl was used
over other methods of kernel-userspace communiction primarily for the
sake of portability.
Porting Notes:
This is ported from Delphix OS change DLPX-44432. The following changes
were made while porting:
- Added ZoL-style ioctl input declaration.
- Reorganized error handling in zpool_initialize in libzfs to integrate
better with changes made for TRIM support.
- Fixed check for whether a checkpoint discard is in progress.
Previously it also waited if the pool had a checkpoint, instead of
just if a checkpoint was being discarded.
- Exposed zfs_initialize_chunk_size as a ZoL-style tunable.
- Updated more existing tests to make use of new 'zpool wait'
functionality, tests that don't exist in Delphix OS.
- Used existing ZoL tunable zfs_scan_suspend_progress, together with
zinject, in place of a new tunable zfs_scan_max_blks_per_txg.
- Added support for a non-integral interval argument to zpool wait.
Future work:
ZoL has support for trimming devices, which Delphix OS does not. In the
future, 'zpool wait' could be extended to add the ability to wait for
trim operations to complete.
Reviewed-by: Matt Ahrens <matt@delphix.com>
Reviewed-by: John Kennedy <john.kennedy@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: John Gallagher <john.gallagher@delphix.com>
Closes #9162
2019-09-14 01:09:06 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_wait/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_wait/scan/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_user/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_user/misc/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_user/zfs_list/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_user/zpool_iostat/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/cli_user/zpool_list/Makefile
|
2019-07-19 18:21:54 +00:00
|
|
|
tests/zfs-tests/tests/functional/cli_user/zpool_status/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/compression/Makefile
|
Fix ENOSPC in "Handle zap_add() failures in ..."
Commit cc63068 caused ENOSPC error when copy a large amount of files
between two directories. The reason is that the patch limits zap leaf
expansion to 2 retries, and return ENOSPC when failed.
The intent for limiting retries is to prevent pointlessly growing table
to max size when adding a block full of entries with same name in
different case in mixed mode. However, it turns out we cannot use any
limit on the retry. When we copy files from one directory in readdir
order, we are copying in hash order, one leaf block at a time. Which
means that if the leaf block in source directory has expanded 6 times,
and you copy those entries in that block, by the time you need to expand
the leaf in destination directory, you need to expand it 6 times in one
go. So any limit on the retry will result in error where it shouldn't.
Note that while we do use different salt for different directories, it
seems that the salt/hash function doesn't provide enough randomization
to the hash distance to prevent this from happening.
Since cc63068 has already been reverted. This patch adds it back and
removes the retry limit.
Also, as it turn out, failing on zap_add() has a serious side effect for
mzap_upgrade(). When upgrading from micro zap to fat zap, it will
call zap_add() to transfer entries one at a time. If it hit any error
halfway through, the remaining entries will be lost, causing those files
to become orphan. This patch add a VERIFY to catch it.
Reviewed-by: Sanjeev Bagewadi <sanjeev.bagewadi@gmail.com>
Reviewed-by: Richard Yao <ryao@gentoo.org>
Reviewed-by: Tony Hutter <hutter2@llnl.gov>
Reviewed-by: Albert Lee <trisk@forkgnu.org>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Signed-off-by: Chunwei Chen <david.chen@nutanix.com>
Closes #7401
Closes #7421
2018-04-18 21:19:50 +00:00
|
|
|
tests/zfs-tests/tests/functional/cp_files/Makefile
|
2021-07-26 20:08:52 +00:00
|
|
|
tests/zfs-tests/tests/functional/crtime/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/ctime/Makefile
|
2017-12-18 22:06:07 +00:00
|
|
|
tests/zfs-tests/tests/functional/deadman/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/delegate/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/devices/Makefile
|
Expose additional file level attributes
ZFS allows to update and retrieve additional file level attributes for
FreeBSD. This commit allows additional file level attributes to be
updated and retrieved for Linux. These include the flags stored in the
upper half of z_pflags only.
Two new IOCTLs have been added for this purpose. ZFS_IOC_GETDOSFLAGS
can be used to retrieve the attributes, while ZFS_IOC_SETDOSFLAGS can
be used to update the attributes.
Attributes that are allowed to be updated include ZFS_IMMUTABLE,
ZFS_APPENDONLY, ZFS_NOUNLINK, ZFS_ARCHIVE, ZFS_NODUMP, ZFS_SYSTEM,
ZFS_HIDDEN, ZFS_READONLY, ZFS_REPARSE, ZFS_OFFLINE and ZFS_SPARSE.
Flags can be or'd together while calling ZFS_IOC_SETDOSFLAGS.
Reviewed-by: Alexander Motin <mav@FreeBSD.org>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Ryan Moeller <ryan@iXsystems.com>
Signed-off-by: Umer Saleem <usaleem@ixsystems.com>
Closes #13118
2022-03-08 01:52:03 +00:00
|
|
|
tests/zfs-tests/tests/functional/dos_attributes/Makefile
|
2017-05-18 19:57:21 +00:00
|
|
|
tests/zfs-tests/tests/functional/events/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/exec/Makefile
|
linux: add basic fallocate(mode=0/2) compatibility
Implement semi-compatible functionality for mode=0 (preallocation)
and mode=FALLOC_FL_KEEP_SIZE (preallocation beyond EOF) for ZPL.
Since ZFS does COW and snapshots, preallocating blocks for a file
cannot guarantee that writes to the file will not run out of space.
Even if the first overwrite was guaranteed, it would not handle any
later overwrite of blocks due to COW, so strict compliance is futile.
Instead, make a best-effort check that at least enough free space is
currently available in the pool (with a bit of margin), then create
a sparse file of the requested size and continue on with life.
This does not handle all cases (e.g. several fallocate() calls before
writing into the files when the filesystem is nearly full), which
would require a more complex mechanism to be implemented, probably
based on a modified version of dmu_prealloc(), but is usable as-is.
A new module option zfs_fallocate_reserve_percent is used to control
the reserve margin for any single fallocate call. By default, this
is 110% of the requested preallocation size, so an additional 10% of
available space is reserved for overhead to allow the application a
good chance of finishing the write when the fallocate() succeeds.
If the heuristics of this basic fallocate implementation are not
desirable, the old non-functional behavior of returning EOPNOTSUPP
for calls can be restored by setting zfs_fallocate_reserve_percent=0.
The parameter of zfs_statvfs() is changed to take an inode instead
of a dentry, since no dentry is available in zfs_fallocate_common().
A few tests from @behlendorf cover basic fallocate functionality.
Reviewed-by: Richard Laager <rlaager@wiktel.com>
Reviewed-by: Arshad Hussain <arshad.super@gmail.com>
Reviewed-by: Matthew Ahrens <mahrens@delphix.com>
Co-authored-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Andreas Dilger <adilger@dilger.ca>
Issue #326
Closes #10408
2020-06-18 18:22:11 +00:00
|
|
|
tests/zfs-tests/tests/functional/fallocate/Makefile
|
2016-09-23 20:51:08 +00:00
|
|
|
tests/zfs-tests/tests/functional/fault/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/features/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/features/async_destroy/Makefile
|
Implement large_dnode pool feature
Justification
-------------
This feature adds support for variable length dnodes. Our motivation is
to eliminate the overhead associated with using spill blocks. Spill
blocks are used to store system attribute data (i.e. file metadata) that
does not fit in the dnode's bonus buffer. By allowing a larger bonus
buffer area the use of a spill block can be avoided. Spill blocks
potentially incur an additional read I/O for every dnode in a dnode
block. As a worst case example, reading 32 dnodes from a 16k dnode block
and all of the spill blocks could issue 33 separate reads. Now suppose
those dnodes have size 1024 and therefore don't need spill blocks. Then
the worst case number of blocks read is reduced to from 33 to two--one
per dnode block. In practice spill blocks may tend to be co-located on
disk with the dnode blocks so the reduction in I/O would not be this
drastic. In a badly fragmented pool, however, the improvement could be
significant.
ZFS-on-Linux systems that make heavy use of extended attributes would
benefit from this feature. In particular, ZFS-on-Linux supports the
xattr=sa dataset property which allows file extended attribute data
to be stored in the dnode bonus buffer as an alternative to the
traditional directory-based format. Workloads such as SELinux and the
Lustre distributed filesystem often store enough xattr data to force
spill bocks when xattr=sa is in effect. Large dnodes may therefore
provide a performance benefit to such systems.
Other use cases that may benefit from this feature include files with
large ACLs and symbolic links with long target names. Furthermore,
this feature may be desirable on other platforms in case future
applications or features are developed that could make use of a
larger bonus buffer area.
Implementation
--------------
The size of a dnode may be a multiple of 512 bytes up to the size of
a dnode block (currently 16384 bytes). A dn_extra_slots field was
added to the current on-disk dnode_phys_t structure to describe the
size of the physical dnode on disk. The 8 bits for this field were
taken from the zero filled dn_pad2 field. The field represents how
many "extra" dnode_phys_t slots a dnode consumes in its dnode block.
This convention results in a value of 0 for 512 byte dnodes which
preserves on-disk format compatibility with older software.
Similarly, the in-memory dnode_t structure has a new dn_num_slots field
to represent the total number of dnode_phys_t slots consumed on disk.
Thus dn->dn_num_slots is 1 greater than the corresponding
dnp->dn_extra_slots. This difference in convention was adopted
because, unlike on-disk structures, backward compatibility is not a
concern for in-memory objects, so we used a more natural way to
represent size for a dnode_t.
The default size for newly created dnodes is determined by the value of
a new "dnodesize" dataset property. By default the property is set to
"legacy" which is compatible with older software. Setting the property
to "auto" will allow the filesystem to choose the most suitable dnode
size. Currently this just sets the default dnode size to 1k, but future
code improvements could dynamically choose a size based on observed
workload patterns. Dnodes of varying sizes can coexist within the same
dataset and even within the same dnode block. For example, to enable
automatically-sized dnodes, run
# zfs set dnodesize=auto tank/fish
The user can also specify literal values for the dnodesize property.
These are currently limited to powers of two from 1k to 16k. The
power-of-2 limitation is only for simplicity of the user interface.
Internally the implementation can handle any multiple of 512 up to 16k,
and consumers of the DMU API can specify any legal dnode value.
The size of a new dnode is determined at object allocation time and
stored as a new field in the znode in-memory structure. New DMU
interfaces are added to allow the consumer to specify the dnode size
that a newly allocated object should use. Existing interfaces are
unchanged to avoid having to update every call site and to preserve
compatibility with external consumers such as Lustre. The new
interfaces names are given below. The versions of these functions that
don't take a dnodesize parameter now just call the _dnsize() versions
with a dnodesize of 0, which means use the legacy dnode size.
New DMU interfaces:
dmu_object_alloc_dnsize()
dmu_object_claim_dnsize()
dmu_object_reclaim_dnsize()
New ZAP interfaces:
zap_create_dnsize()
zap_create_norm_dnsize()
zap_create_flags_dnsize()
zap_create_claim_norm_dnsize()
zap_create_link_dnsize()
The constant DN_MAX_BONUSLEN is renamed to DN_OLD_MAX_BONUSLEN. The
spa_maxdnodesize() function should be used to determine the maximum
bonus length for a pool.
These are a few noteworthy changes to key functions:
* The prototype for dnode_hold_impl() now takes a "slots" parameter.
When the DNODE_MUST_BE_FREE flag is set, this parameter is used to
ensure the hole at the specified object offset is large enough to
hold the dnode being created. The slots parameter is also used
to ensure a dnode does not span multiple dnode blocks. In both of
these cases, if a failure occurs, ENOSPC is returned. Keep in mind,
these failure cases are only possible when using DNODE_MUST_BE_FREE.
If the DNODE_MUST_BE_ALLOCATED flag is set, "slots" must be 0.
dnode_hold_impl() will check if the requested dnode is already
consumed as an extra dnode slot by an large dnode, in which case
it returns ENOENT.
* The function dmu_object_alloc() advances to the next dnode block
if dnode_hold_impl() returns an error for a requested object.
This is because the beginning of the next dnode block is the only
location it can safely assume to either be a hole or a valid
starting point for a dnode.
* dnode_next_offset_level() and other functions that iterate
through dnode blocks may no longer use a simple array indexing
scheme. These now use the current dnode's dn_num_slots field to
advance to the next dnode in the block. This is to ensure we
properly skip the current dnode's bonus area and don't interpret it
as a valid dnode.
zdb
---
The zdb command was updated to display a dnode's size under the
"dnsize" column when the object is dumped.
For ZIL create log records, zdb will now display the slot count for
the object.
ztest
-----
Ztest chooses a random dnodesize for every newly created object. The
random distribution is more heavily weighted toward small dnodes to
better simulate real-world datasets.
Unused bonus buffer space is filled with non-zero values computed from
the object number, dataset id, offset, and generation number. This
helps ensure that the dnode traversal code properly skips the interior
regions of large dnodes, and that these interior regions are not
overwritten by data belonging to other dnodes. A new test visits each
object in a dataset. It verifies that the actual dnode size matches what
was stored in the ztest block tag when it was created. It also verifies
that the unused bonus buffer space is filled with the expected data
patterns.
ZFS Test Suite
--------------
Added six new large dnode-specific tests, and integrated the dnodesize
property into existing tests for zfs allow and send/recv.
Send/Receive
------------
ZFS send streams for datasets containing large dnodes cannot be received
on pools that don't support the large_dnode feature. A send stream with
large dnodes sets a DMU_BACKUP_FEATURE_LARGE_DNODE flag which will be
unrecognized by an incompatible receiving pool so that the zfs receive
will fail gracefully.
While not implemented here, it may be possible to generate a
backward-compatible send stream from a dataset containing large
dnodes. The implementation may be tricky, however, because the send
object record for a large dnode would need to be resized to a 512
byte dnode, possibly kicking in a spill block in the process. This
means we would need to construct a new SA layout and possibly
register it in the SA layout object. The SA layout is normally just
sent as an ordinary object record. But if we are constructing new
layouts while generating the send stream we'd have to build the SA
layout object dynamically and send it at the end of the stream.
For sending and receiving between pools that do support large dnodes,
the drr_object send record type is extended with a new field to store
the dnode slot count. This field was repurposed from unused padding
in the structure.
ZIL Replay
----------
The dnode slot count is stored in the uppermost 8 bits of the lr_foid
field. The bits were unused as the object id is currently capped at
48 bits.
Resizing Dnodes
---------------
It should be possible to resize a dnode when it is dirtied if the
current dnodesize dataset property differs from the dnode's size, but
this functionality is not currently implemented. Clearly a dnode can
only grow if there are sufficient contiguous unused slots in the
dnode block, but it should always be possible to shrink a dnode.
Growing dnodes may be useful to reduce fragmentation in a pool with
many spill blocks in use. Shrinking dnodes may be useful to allow
sending a dataset to a pool that doesn't support the large_dnode
feature.
Feature Reference Counting
--------------------------
The reference count for the large_dnode pool feature tracks the
number of datasets that have ever contained a dnode of size larger
than 512 bytes. The first time a large dnode is created in a dataset
the dataset is converted to an extensible dataset. This is a one-way
operation and the only way to decrement the feature count is to
destroy the dataset, even if the dataset no longer contains any large
dnodes. The complexity of reference counting on a per-dnode basis was
too high, so we chose to track it on a per-dataset basis similarly to
the large_block feature.
Signed-off-by: Ned Bass <bass6@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #3542
2016-03-17 01:25:34 +00:00
|
|
|
tests/zfs-tests/tests/functional/features/large_dnode/Makefile
|
2018-06-20 21:03:13 +00:00
|
|
|
tests/zfs-tests/tests/functional/grow/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/history/Makefile
|
2017-09-12 20:15:11 +00:00
|
|
|
tests/zfs-tests/tests/functional/hkdf/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/inheritance/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/inuse/Makefile
|
2018-08-27 17:04:21 +00:00
|
|
|
tests/zfs-tests/tests/functional/io/Makefile
|
Add L2ARC arcstats for MFU/MRU buffers and buffer content type
Currently the ARC state (MFU/MRU) of cached L2ARC buffer and their
content type is unknown. Knowing this information may prove beneficial
in adjusting the L2ARC caching policy.
This commit adds L2ARC arcstats that display the aligned size
(in bytes) of L2ARC buffers according to their content type
(data/metadata) and according to their ARC state (MRU/MFU or
prefetch). It also expands the existing evict_l2_eligible arcstat to
differentiate between MFU and MRU buffers.
L2ARC caches buffers from the MRU and MFU lists of ARC. Upon caching a
buffer, its ARC state (MRU/MFU) is stored in the L2 header
(b_arcs_state). The l2_m{f,r}u_asize arcstats reflect the aligned size
(in bytes) of L2ARC buffers according to their ARC state (based on
b_arcs_state). We also account for the case where an L2ARC and ARC
cached MRU or MRU_ghost buffer transitions to MFU. The l2_prefetch_asize
reflects the alinged size (in bytes) of L2ARC buffers that were cached
while they had the prefetch flag set in ARC. This is dynamically updated
as the prefetch flag of L2ARC buffers changes.
When buffers are evicted from ARC, if they are determined to be L2ARC
eligible then their logical size is recorded in
evict_l2_eligible_m{r,f}u arcstats according to their ARC state upon
eviction.
Persistent L2ARC:
When committing an L2ARC buffer to a log block (L2ARC metadata) its
b_arcs_state and prefetch flag is also stored. If the buffer changes
its arcstate or prefetch flag this is reflected in the above arcstats.
However, the L2ARC metadata cannot currently be updated to reflect this
change.
Example: L2ARC caches an MRU buffer. L2ARC metadata and arcstats count
this as an MRU buffer. The buffer transitions to MFU. The arcstats are
updated to reflect this. Upon pool re-import or on/offlining the L2ARC
device the arcstats are cleared and the buffer will now be counted as an
MRU buffer, as the L2ARC metadata were not updated.
Bug fix:
- If l2arc_noprefetch is set, arc_read_done clears the L2CACHE flag of
an ARC buffer. However, prefetches may be issued in a way that
arc_read_done() is bypassed. Instead, move the related code in
l2arc_write_eligible() to account for those cases too.
Also add a test and update manpages for l2arc_mfuonly module parameter,
and update the manpages and code comments for l2arc_noprefetch.
Move persist_l2arc tests to l2arc.
Reviewed-by: Ryan Moeller <freqlabs@FreeBSD.org>
Reviewed-by: Richard Elling <Richard.Elling@RichardElling.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: George Amanakis <gamanakis@gmail.com>
Closes #10743
2020-09-14 17:10:44 +00:00
|
|
|
tests/zfs-tests/tests/functional/l2arc/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/large_files/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/largest_pool/Makefile
|
2015-03-11 10:02:08 +00:00
|
|
|
tests/zfs-tests/tests/functional/libzfs/Makefile
|
2019-01-08 18:17:46 +00:00
|
|
|
tests/zfs-tests/tests/functional/limits/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/link_count/Makefile
|
Log Spacemap Project
= Motivation
At Delphix we've seen a lot of customer systems where fragmentation
is over 75% and random writes take a performance hit because a lot
of time is spend on I/Os that update on-disk space accounting metadata.
Specifically, we seen cases where 20% to 40% of sync time is spend
after sync pass 1 and ~30% of the I/Os on the system is spent updating
spacemaps.
The problem is that these pools have existed long enough that we've
touched almost every metaslab at least once, and random writes
scatter frees across all metaslabs every TXG, thus appending to
their spacemaps and resulting in many I/Os. To give an example,
assuming that every VDEV has 200 metaslabs and our writes fit within
a single spacemap block (generally 4K) we have 200 I/Os. Then if we
assume 2 levels of indirection, we need 400 additional I/Os and
since we are talking about metadata for which we keep 2 extra copies
for redundancy we need to triple that number, leading to a total of
1800 I/Os per VDEV every TXG.
We could try and decrease the number of metaslabs so we have less
I/Os per TXG but then each metaslab would cover a wider range on
disk and thus would take more time to be loaded in memory from disk.
In addition, after it's loaded, it's range tree would consume more
memory.
Another idea would be to just increase the spacemap block size
which would allow us to fit more entries within an I/O block
resulting in fewer I/Os per metaslab and a speedup in loading time.
The problem is still that we don't deal with the number of I/Os
going up as the number of metaslabs is increasing and the fact
is that we generally write a lot to a few metaslabs and a little
to the rest of them. Thus, just increasing the block size would
actually waste bandwidth because we won't be utilizing our bigger
block size.
= About this patch
This patch introduces the Log Spacemap project which provides the
solution to the above problem while taking into account all the
aforementioned tradeoffs. The details on how it achieves that can
be found in the references sections below and in the code (see
Big Theory Statement in spa_log_spacemap.c).
Even though the change is fairly constraint within the metaslab
and lower-level SPA codepaths, there is a side-change that is
user-facing. The change is that VDEV IDs from VDEV holes will no
longer be reused. To give some background and reasoning for this,
when a log device is removed and its VDEV structure was replaced
with a hole (or was compacted; if at the end of the vdev array),
its vdev_id could be reused by devices added after that. Now
with the pool-wide space maps recording the vdev ID, this behavior
can cause problems (e.g. is this entry referring to a segment in
the new vdev or the removed log?). Thus, to simplify things the
ID reuse behavior is gone and now vdev IDs for top-level vdevs
are truly unique within a pool.
= Testing
The illumos implementation of this feature has been used internally
for a year and has been in production for ~6 months. For this patch
specifically there don't seem to be any regressions introduced to
ZTS and I have been running zloop for a week without any related
problems.
= Performance Analysis (Linux Specific)
All performance results and analysis for illumos can be found in
the links of the references. Redoing the same experiments in Linux
gave similar results. Below are the specifics of the Linux run.
After the pool reached stable state the percentage of the time
spent in pass 1 per TXG was 64% on average for the stock bits
while the log spacemap bits stayed at 95% during the experiment
(graph: sdimitro.github.io/img/linux-lsm/PercOfSyncInPassOne.png).
Sync times per TXG were 37.6 seconds on average for the stock
bits and 22.7 seconds for the log spacemap bits (related graph:
sdimitro.github.io/img/linux-lsm/SyncTimePerTXG.png). As a result
the log spacemap bits were able to push more TXGs, which is also
the reason why all graphs quantified per TXG have more entries for
the log spacemap bits.
Another interesting aspect in terms of txg syncs is that the stock
bits had 22% of their TXGs reach sync pass 7, 55% reach sync pass 8,
and 20% reach 9. The log space map bits reached sync pass 4 in 79%
of their TXGs, sync pass 7 in 19%, and sync pass 8 at 1%. This
emphasizes the fact that not only we spend less time on metadata
but we also iterate less times to convergence in spa_sync() dirtying
objects.
[related graphs:
stock- sdimitro.github.io/img/linux-lsm/NumberOfPassesPerTXGStock.png
lsm- sdimitro.github.io/img/linux-lsm/NumberOfPassesPerTXGLSM.png]
Finally, the improvement in IOPs that the userland gains from the
change is approximately 40%. There is a consistent win in IOPS as
you can see from the graphs below but the absolute amount of
improvement that the log spacemap gives varies within each minute
interval.
sdimitro.github.io/img/linux-lsm/StockVsLog3Days.png
sdimitro.github.io/img/linux-lsm/StockVsLog10Hours.png
= Porting to Other Platforms
For people that want to port this commit to other platforms below
is a list of ZoL commits that this patch depends on:
Make zdb results for checkpoint tests consistent
db587941c5ff6dea01932bb78f70db63cf7f38ba
Update vdev_is_spacemap_addressable() for new spacemap encoding
419ba5914552c6185afbe1dd17b3ed4b0d526547
Simplify spa_sync by breaking it up to smaller functions
8dc2197b7b1e4d7ebc1420ea30e51c6541f1d834
Factor metaslab_load_wait() in metaslab_load()
b194fab0fb6caad18711abccaff3c69ad8b3f6d3
Rename range_tree_verify to range_tree_verify_not_present
df72b8bebe0ebac0b20e0750984bad182cb6564a
Change target size of metaslabs from 256GB to 16GB
c853f382db731e15a87512f4ef1101d14d778a55
zdb -L should skip leak detection altogether
21e7cf5da89f55ce98ec1115726b150e19eefe89
vs_alloc can underflow in L2ARC vdevs
7558997d2f808368867ca7e5234e5793446e8f3f
Simplify log vdev removal code
6c926f426a26ffb6d7d8e563e33fc176164175cb
Get rid of space_map_update() for ms_synced_length
425d3237ee88abc53d8522a7139c926d278b4b7f
Introduce auxiliary metaslab histograms
928e8ad47d3478a3d5d01f0dd6ae74a9371af65e
Error path in metaslab_load_impl() forgets to drop ms_sync_lock
8eef997679ba54547f7d361553d21b3291f41ae7
= References
Background, Motivation, and Internals of the Feature
- OpenZFS 2017 Presentation:
youtu.be/jj2IxRkl5bQ
- Slides:
slideshare.net/SerapheimNikolaosDim/zfs-log-spacemaps-project
Flushing Algorithm Internals & Performance Results
(Illumos Specific)
- Blogpost:
sdimitro.github.io/post/zfs-lsm-flushing/
- OpenZFS 2018 Presentation:
youtu.be/x6D2dHRjkxw
- Slides:
slideshare.net/SerapheimNikolaosDim/zfs-log-spacemap-flushing-algorithm
Upstream Delphix Issues:
DLPX-51539, DLPX-59659, DLPX-57783, DLPX-61438, DLPX-41227, DLPX-59320
DLPX-63385
Reviewed-by: Sean Eric Fagan <sef@ixsystems.com>
Reviewed-by: Matt Ahrens <matt@delphix.com>
Reviewed-by: George Wilson <gwilson@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Serapheim Dimitropoulos <serapheim@delphix.com>
Closes #8442
2019-07-16 17:11:49 +00:00
|
|
|
tests/zfs-tests/tests/functional/log_spacemap/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/migration/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/mmap/Makefile
|
Multi-modifier protection (MMP)
Add multihost=on|off pool property to control MMP. When enabled
a new thread writes uberblocks to the last slot in each label, at a
set frequency, to indicate to other hosts the pool is actively imported.
These uberblocks are the last synced uberblock with an updated
timestamp. Property defaults to off.
During tryimport, find the "best" uberblock (newest txg and timestamp)
repeatedly, checking for change in the found uberblock. Include the
results of the activity test in the config returned by tryimport.
These results are reported to user in "zpool import".
Allow the user to control the period between MMP writes, and the
duration of the activity test on import, via a new module parameter
zfs_multihost_interval. The period is specified in milliseconds. The
activity test duration is calculated from this value, and from the
mmp_delay in the "best" uberblock found initially.
Add a kstat interface to export statistics about Multiple Modifier
Protection (MMP) updates. Include the last synced txg number, the
timestamp, the delay since the last MMP update, the VDEV GUID, the VDEV
label that received the last MMP update, and the VDEV path. Abbreviated
output below.
$ cat /proc/spl/kstat/zfs/mypool/multihost
31 0 0x01 10 880 105092382393521 105144180101111
txg timestamp mmp_delay vdev_guid vdev_label vdev_path
20468 261337 250274925 68396651780 3 /dev/sda
20468 261339 252023374 6267402363293 1 /dev/sdc
20468 261340 252000858 6698080955233 1 /dev/sdx
20468 261341 251980635 783892869810 2 /dev/sdy
20468 261342 253385953 8923255792467 3 /dev/sdd
20468 261344 253336622 042125143176 0 /dev/sdab
20468 261345 253310522 1200778101278 2 /dev/sde
20468 261346 253286429 0950576198362 2 /dev/sdt
20468 261347 253261545 96209817917 3 /dev/sds
20468 261349 253238188 8555725937673 3 /dev/sdb
Add a new tunable zfs_multihost_history to specify the number of MMP
updates to store history for. By default it is set to zero meaning that
no MMP statistics are stored.
When using ztest to generate activity, for automated tests of the MMP
function, some test functions interfere with the test. For example, the
pool is exported to run zdb and then imported again. Add a new ztest
function, "-M", to alter ztest behavior to prevent this.
Add new tests to verify the new functionality. Tests provided by
Giuseppe Di Natale.
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Reviewed-by: Ned Bass <bass6@llnl.gov>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Olaf Faaland <faaland1@llnl.gov>
Closes #745
Closes #6279
2017-07-08 03:20:35 +00:00
|
|
|
tests/zfs-tests/tests/functional/mmp/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/mount/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/mv_files/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/nestedfs/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/no_space/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/nopwrite/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/online_offline/Makefile
|
2020-06-25 01:45:44 +00:00
|
|
|
tests/zfs-tests/tests/functional/pam/Makefile
|
2016-12-16 22:11:29 +00:00
|
|
|
tests/zfs-tests/tests/functional/pool_checkpoint/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/pool_names/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/poolversion/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/privilege/Makefile
|
2018-09-26 18:08:12 +00:00
|
|
|
tests/zfs-tests/tests/functional/procfs/Makefile
|
2018-02-13 22:54:54 +00:00
|
|
|
tests/zfs-tests/tests/functional/projectquota/Makefile
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
tests/zfs-tests/tests/functional/pyzfs/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/quota/Makefile
|
SIMD implementation of vdev_raidz generate and reconstruct routines
This is a new implementation of RAIDZ1/2/3 routines using x86_64
scalar, SSE, and AVX2 instruction sets. Included are 3 parity
generation routines (P, PQ, and PQR) and 7 reconstruction routines,
for all RAIDZ level. On module load, a quick benchmark of supported
routines will select the fastest for each operation and they will
be used at runtime. Original implementation is still present and
can be selected via module parameter.
Patch contains:
- specialized gen/rec routines for all RAIDZ levels,
- new scalar raidz implementation (unrolled),
- two x86_64 SIMD implementations (SSE and AVX2 instructions sets),
- fastest routines selected on module load (benchmark).
- cmd/raidz_test - verify and benchmark all implementations
- added raidz_test to the ZFS Test Suite
New zfs module parameters:
- zfs_vdev_raidz_impl (str): selects the implementation to use. On
module load, the parameter will only accept first 3 options, and
the other implementations can be set once module is finished
loading. Possible values for this option are:
"fastest" - use the fastest math available
"original" - use the original raidz code
"scalar" - new scalar impl
"sse" - new SSE impl if available
"avx2" - new AVX2 impl if available
See contents of `/sys/module/zfs/parameters/zfs_vdev_raidz_impl` to
get the list of supported values. If an implementation is not supported
on the system, it will not be shown. Currently selected option is
enclosed in `[]`.
Signed-off-by: Gvozden Neskovic <neskovic@gmail.com>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #4328
2016-04-25 08:04:31 +00:00
|
|
|
tests/zfs-tests/tests/functional/raidz/Makefile
|
Implement Redacted Send/Receive
Redacted send/receive allows users to send subsets of their data to
a target system. One possible use case for this feature is to not
transmit sensitive information to a data warehousing, test/dev, or
analytics environment. Another is to save space by not replicating
unimportant data within a given dataset, for example in backup tools
like zrepl.
Redacted send/receive is a three-stage process. First, a clone (or
clones) is made of the snapshot to be sent to the target. In this
clone (or clones), all unnecessary or unwanted data is removed or
modified. This clone is then snapshotted to create the "redaction
snapshot" (or snapshots). Second, the new zfs redact command is used
to create a redaction bookmark. The redaction bookmark stores the
list of blocks in a snapshot that were modified by the redaction
snapshot(s). Finally, the redaction bookmark is passed as a parameter
to zfs send. When sending to the snapshot that was redacted, the
redaction bookmark is used to filter out blocks that contain sensitive
or unwanted information, and those blocks are not included in the send
stream. When sending from the redaction bookmark, the blocks it
contains are considered as candidate blocks in addition to those
blocks in the destination snapshot that were modified since the
creation_txg of the redaction bookmark. This step is necessary to
allow the target to rehydrate data in the case where some blocks are
accidentally or unnecessarily modified in the redaction snapshot.
The changes to bookmarks to enable fast space estimation involve
adding deadlists to bookmarks. There is also logic to manage the
life cycles of these deadlists.
The new size estimation process operates in cases where previously
an accurate estimate could not be provided. In those cases, a send
is performed where no data blocks are read, reducing the runtime
significantly and providing a byte-accurate size estimate.
Reviewed-by: Dan Kimmel <dan.kimmel@delphix.com>
Reviewed-by: Matt Ahrens <mahrens@delphix.com>
Reviewed-by: Prashanth Sreenivasa <pks@delphix.com>
Reviewed-by: John Kennedy <john.kennedy@delphix.com>
Reviewed-by: George Wilson <george.wilson@delphix.com>
Reviewed-by: Chris Williamson <chris.williamson@delphix.com>
Reviewed-by: Pavel Zhakarov <pavel.zakharov@delphix.com>
Reviewed-by: Sebastien Roy <sebastien.roy@delphix.com>
Reviewed-by: Prakash Surya <prakash.surya@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Paul Dagnelie <pcd@delphix.com>
Closes #7958
2019-06-19 16:48:13 +00:00
|
|
|
tests/zfs-tests/tests/functional/redacted_send/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/redundancy/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/refquota/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/refreserv/Makefile
|
OpenZFS 7614, 9064 - zfs device evacuation/removal
OpenZFS 7614 - zfs device evacuation/removal
OpenZFS 9064 - remove_mirror should wait for device removal to complete
This project allows top-level vdevs to be removed from the storage pool
with "zpool remove", reducing the total amount of storage in the pool.
This operation copies all allocated regions of the device to be removed
onto other devices, recording the mapping from old to new location.
After the removal is complete, read and free operations to the removed
(now "indirect") vdev must be remapped and performed at the new location
on disk. The indirect mapping table is kept in memory whenever the pool
is loaded, so there is minimal performance overhead when doing operations
on the indirect vdev.
The size of the in-memory mapping table will be reduced when its entries
become "obsolete" because they are no longer used by any block pointers
in the pool. An entry becomes obsolete when all the blocks that use
it are freed. An entry can also become obsolete when all the snapshots
that reference it are deleted, and the block pointers that reference it
have been "remapped" in all filesystems/zvols (and clones). Whenever an
indirect block is written, all the block pointers in it will be "remapped"
to their new (concrete) locations if possible. This process can be
accelerated by using the "zfs remap" command to proactively rewrite all
indirect blocks that reference indirect (removed) vdevs.
Note that when a device is removed, we do not verify the checksum of
the data that is copied. This makes the process much faster, but if it
were used on redundant vdevs (i.e. mirror or raidz vdevs), it would be
possible to copy the wrong data, when we have the correct data on e.g.
the other side of the mirror.
At the moment, only mirrors and simple top-level vdevs can be removed
and no removal is allowed if any of the top-level vdevs are raidz.
Porting Notes:
* Avoid zero-sized kmem_alloc() in vdev_compact_children().
The device evacuation code adds a dependency that
vdev_compact_children() be able to properly empty the vdev_child
array by setting it to NULL and zeroing vdev_children. Under Linux,
kmem_alloc() and related functions return a sentinel pointer rather
than NULL for zero-sized allocations.
* Remove comment regarding "mpt" driver where zfs_remove_max_segment
is initialized to SPA_MAXBLOCKSIZE.
Change zfs_condense_indirect_commit_entry_delay_ticks to
zfs_condense_indirect_commit_entry_delay_ms for consistency with
most other tunables in which delays are specified in ms.
* ZTS changes:
Use set_tunable rather than mdb
Use zpool sync as appropriate
Use sync_pool instead of sync
Kill jobs during test_removal_with_operation to allow unmount/export
Don't add non-disk names such as "mirror" or "raidz" to $DISKS
Use $TEST_BASE_DIR instead of /tmp
Increase HZ from 100 to 1000 which is more common on Linux
removal_multiple_indirection.ksh
Reduce iterations in order to not time out on the code
coverage builders.
removal_resume_export:
Functionally, the test case is correct but there exists a race
where the kernel thread hasn't been fully started yet and is
not visible. Wait for up to 1 second for the removal thread
to be started before giving up on it. Also, increase the
amount of data copied in order that the removal not finish
before the export has a chance to fail.
* MMP compatibility, the concept of concrete versus non-concrete devices
has slightly changed the semantics of vdev_writeable(). Update
mmp_random_leaf_impl() accordingly.
* Updated dbuf_remap() to handle the org.zfsonlinux:large_dnode pool
feature which is not supported by OpenZFS.
* Added support for new vdev removal tracepoints.
* Test cases removal_with_zdb and removal_condense_export have been
intentionally disabled. When run manually they pass as intended,
but when running in the automated test environment they produce
unreliable results on the latest Fedora release.
They may work better once the upstream pool import refectoring is
merged into ZoL at which point they will be re-enabled.
Authored by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Alex Reece <alex@delphix.com>
Reviewed-by: George Wilson <george.wilson@delphix.com>
Reviewed-by: John Kennedy <john.kennedy@delphix.com>
Reviewed-by: Prakash Surya <prakash.surya@delphix.com>
Reviewed by: Richard Laager <rlaager@wiktel.com>
Reviewed by: Tim Chase <tim@chase2k.com>
Reviewed by: Brian Behlendorf <behlendorf1@llnl.gov>
Approved by: Garrett D'Amore <garrett@damore.org>
Ported-by: Tim Chase <tim@chase2k.com>
Signed-off-by: Tim Chase <tim@chase2k.com>
OpenZFS-issue: https://www.illumos.org/issues/7614
OpenZFS-commit: https://github.com/openzfs/openzfs/commit/f539f1eb
Closes #6900
2016-09-22 16:30:13 +00:00
|
|
|
tests/zfs-tests/tests/functional/removal/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/rename_dirs/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/replacement/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/reservation/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/rootpool/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/rsend/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/scrub_mirror/Makefile
|
2022-02-09 20:50:10 +00:00
|
|
|
tests/zfs-tests/tests/functional/simd/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/slog/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/snapshot/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/snapused/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/sparse/Makefile
|
2021-12-18 00:18:37 +00:00
|
|
|
tests/zfs-tests/tests/functional/stat/Makefile
|
2019-07-26 20:52:30 +00:00
|
|
|
tests/zfs-tests/tests/functional/suid/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/threadsappend/Makefile
|
2016-01-26 20:29:46 +00:00
|
|
|
tests/zfs-tests/tests/functional/tmpfile/Makefile
|
2019-03-29 16:13:20 +00:00
|
|
|
tests/zfs-tests/tests/functional/trim/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/truncate/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/upgrade/Makefile
|
2018-03-07 23:40:42 +00:00
|
|
|
tests/zfs-tests/tests/functional/user_namespace/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/userquota/Makefile
|
2016-04-11 20:16:57 +00:00
|
|
|
tests/zfs-tests/tests/functional/vdev_zaps/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/write_dirs/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/xattr/Makefile
|
2020-10-09 16:29:21 +00:00
|
|
|
tests/zfs-tests/tests/functional/zpool_influxdb/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/zvol/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_ENOSPC/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_cli/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_misc/Makefile
|
|
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_swap/Makefile
|
2016-08-03 21:26:15 +00:00
|
|
|
tests/zfs-tests/tests/perf/Makefile
|
|
|
|
|
tests/zfs-tests/tests/perf/fio/Makefile
|
|
|
|
|
tests/zfs-tests/tests/perf/regression/Makefile
|
|
|
|
|
tests/zfs-tests/tests/perf/scripts/Makefile
|
2015-07-01 22:23:09 +00:00
|
|
|
tests/zfs-tests/tests/stress/Makefile
|
2019-10-09 17:54:22 +00:00
|
|
|
udev/Makefile
|
|
|
|
|
udev/rules.d/Makefile
|
2012-07-12 19:21:25 +00:00
|
|
|
zfs.release
|
2010-08-26 18:22:58 +00:00
|
|
|
])
|
|
|
|
|
|
2016-10-19 19:55:59 +00:00
|
|
|
|
2010-08-26 18:22:58 +00:00
|
|
|
AC_OUTPUT
|
