2010-08-26 22:22:58 +04:00
|
|
|
/*
|
|
|
|
* This file is part of the ZFS Linux port.
|
|
|
|
*
|
|
|
|
* 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
|
|
|
|
*/
|
|
|
|
|
2018-05-31 06:11:19 +03:00
|
|
|
AC_INIT(m4_esyscmd(grep ^Name: META | cut -d ':' -f 2 | tr -d ' \n'),
|
|
|
|
m4_esyscmd(grep ^Version: META | cut -d ':' -f 2 | tr -d ' \n'))
|
2010-08-26 22:22:58 +04:00
|
|
|
AC_LANG(C)
|
|
|
|
ZFS_AC_META
|
|
|
|
AC_CONFIG_AUX_DIR([config])
|
2013-03-30 06:33:09 +04:00
|
|
|
AC_CONFIG_MACRO_DIR([config])
|
2010-08-26 22:22:58 +04:00
|
|
|
AC_CANONICAL_SYSTEM
|
|
|
|
AM_MAINTAINER_MODE
|
2013-04-03 02:16:39 +04:00
|
|
|
m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
|
2016-05-12 17:51:24 +03:00
|
|
|
AM_INIT_AUTOMAKE([subdir-objects])
|
2010-08-26 22:22:58 +04:00
|
|
|
AC_CONFIG_HEADERS([zfs_config.h], [
|
|
|
|
(mv zfs_config.h zfs_config.h.tmp &&
|
2010-09-05 00:26:23 +04:00
|
|
|
awk -f ${ac_srcdir}/config/config.awk zfs_config.h.tmp >zfs_config.h &&
|
2010-08-26 22:22:58 +04:00
|
|
|
rm zfs_config.h.tmp) || exit 1])
|
|
|
|
|
|
|
|
AC_PROG_INSTALL
|
|
|
|
AC_PROG_CC
|
|
|
|
AC_PROG_LIBTOOL
|
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 03:19:05 +03:00
|
|
|
PKG_PROG_PKG_CONFIG
|
2010-08-26 22:22:58 +04:00
|
|
|
AM_PROG_AS
|
2016-06-16 01:47:05 +03:00
|
|
|
AM_PROG_CC_C_O
|
2017-09-23 04:49:57 +03:00
|
|
|
AX_CODE_COVERAGE
|
2018-08-15 19:52:28 +03:00
|
|
|
_AM_PROG_TAR(pax)
|
2010-08-26 22:22:58 +04:00
|
|
|
|
|
|
|
ZFS_AC_LICENSE
|
|
|
|
ZFS_AC_PACKAGE
|
|
|
|
ZFS_AC_CONFIG
|
|
|
|
ZFS_AC_DEBUG
|
2014-09-23 22:29:30 +04:00
|
|
|
ZFS_AC_DEBUGINFO
|
2018-02-16 04:53:18 +03:00
|
|
|
ZFS_AC_DEBUG_KMEM
|
|
|
|
ZFS_AC_DEBUG_KMEM_TRACKING
|
2010-08-26 22:22:58 +04:00
|
|
|
|
2015-07-02 01:23:09 +03:00
|
|
|
AC_CONFIG_FILES([
|
2010-08-26 22:22:58 +04:00
|
|
|
Makefile
|
2011-08-05 23:22:58 +04:00
|
|
|
udev/Makefile
|
|
|
|
udev/rules.d/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
etc/Makefile
|
2011-03-18 01:02:28 +03:00
|
|
|
etc/init.d/Makefile
|
|
|
|
etc/zfs/Makefile
|
2014-01-19 18:36:49 +04:00
|
|
|
etc/systemd/Makefile
|
|
|
|
etc/systemd/system/Makefile
|
2018-04-07 00:11:09 +03:00
|
|
|
etc/systemd/system-generators/Makefile
|
2017-06-05 20:52:15 +03:00
|
|
|
etc/sudoers.d/Makefile
|
2014-01-19 18:36:49 +04:00
|
|
|
etc/modules-load.d/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
man/Makefile
|
2013-03-12 23:40:55 +04:00
|
|
|
man/man1/Makefile
|
2012-04-21 04:32:30 +04:00
|
|
|
man/man5/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
man/man8/Makefile
|
|
|
|
lib/Makefile
|
2010-08-26 22:50:56 +04:00
|
|
|
lib/libspl/Makefile
|
|
|
|
lib/libspl/asm-generic/Makefile
|
|
|
|
lib/libspl/asm-i386/Makefile
|
|
|
|
lib/libspl/asm-x86_64/Makefile
|
|
|
|
lib/libspl/include/Makefile
|
2010-09-05 00:26:23 +04:00
|
|
|
lib/libspl/include/ia32/Makefile
|
|
|
|
lib/libspl/include/ia32/sys/Makefile
|
|
|
|
lib/libspl/include/rpc/Makefile
|
|
|
|
lib/libspl/include/sys/Makefile
|
|
|
|
lib/libspl/include/sys/dktp/Makefile
|
|
|
|
lib/libspl/include/util/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
lib/libavl/Makefile
|
|
|
|
lib/libefi/Makefile
|
2016-05-12 17:51:24 +03:00
|
|
|
lib/libicp/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
lib/libnvpair/Makefile
|
2018-11-05 22:22:33 +03:00
|
|
|
lib/libzutil/Makefile
|
2017-08-10 01:31:08 +03:00
|
|
|
lib/libtpool/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
lib/libunicode/Makefile
|
|
|
|
lib/libuutil/Makefile
|
|
|
|
lib/libzpool/Makefile
|
2014-06-07 03:23:22 +04:00
|
|
|
lib/libzfs/libzfs.pc
|
|
|
|
lib/libzfs/libzfs_core.pc
|
2010-08-26 22:22:58 +04:00
|
|
|
lib/libzfs/Makefile
|
2013-08-28 15:45:09 +04:00
|
|
|
lib/libzfs_core/Makefile
|
2011-07-02 23:34:05 +04:00
|
|
|
lib/libshare/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
cmd/Makefile
|
|
|
|
cmd/zdb/Makefile
|
2012-12-14 03:24:15 +04:00
|
|
|
cmd/zhack/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
cmd/zfs/Makefile
|
|
|
|
cmd/zinject/Makefile
|
|
|
|
cmd/zpool/Makefile
|
2012-08-29 23:23:12 +04:00
|
|
|
cmd/zstreamdump/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
cmd/ztest/Makefile
|
2011-03-05 02:14:46 +03:00
|
|
|
cmd/mount_zfs/Makefile
|
2013-01-10 00:51:29 +04:00
|
|
|
cmd/fsck_zfs/Makefile
|
2011-02-22 13:58:44 +03:00
|
|
|
cmd/zvol_id/Makefile
|
2012-04-21 04:32:30 +04:00
|
|
|
cmd/vdev_id/Makefile
|
2013-06-07 08:33:01 +04:00
|
|
|
cmd/arcstat/Makefile
|
2013-10-26 00:58:45 +04:00
|
|
|
cmd/dbufstat/Makefile
|
2015-03-03 00:28:57 +03:00
|
|
|
cmd/arc_summary/Makefile
|
2014-01-22 01:30:03 +04:00
|
|
|
cmd/zed/Makefile
|
2019-06-24 19:32:47 +03:00
|
|
|
cmd/zed/zed.d/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 11:04:31 +03:00
|
|
|
cmd/raidz_test/Makefile
|
2017-07-19 04:11:08 +03:00
|
|
|
cmd/zgenhostid/Makefile
|
2019-07-18 01:33:05 +03:00
|
|
|
cmd/zvol_wait/Makefile
|
2014-07-19 03:45:49 +04:00
|
|
|
contrib/Makefile
|
|
|
|
contrib/bash_completion.d/Makefile
|
2015-07-09 21:41:14 +03:00
|
|
|
contrib/dracut/Makefile
|
2016-03-31 02:59:15 +03:00
|
|
|
contrib/dracut/02zfsexpandknowledge/Makefile
|
2015-07-09 21:41:14 +03:00
|
|
|
contrib/dracut/90zfs/Makefile
|
Initramfs scripts for ZoL.
* Supports booting of a ZFS snapshot.
Do this by cloning the snapshot into a dataset. If this, the resulting
dataset, already exists, destroy it. Then mount it on root.
* If snapshot does not exist, use base dataset (the part before '@')
as boot filesystem instead.
* If no snapshot is specified on the 'root=' kernel command line, but there
is an '@', then get a list of snapshots below that filesystem and ask the
user which to use.
* Clone with 'mountpoint=none' and 'canmount=noauto' - we mount manually
and explicitly.
* For sub-filesystems, that doesn't have a mountpoint property set, we use
the 'org.zol:mountpoint' to keep track of it's mountpoint.
* Allow rollback of snapshots instead of clone it and boot from the clone.
* Allow mounting a root- and subfs with mountpoint=legacy set
* Allow mounting a filesystem which is using nativ encryption.
* Support all currently used kernel command line arguments
All the different distributions have their own standard on what to specify
on the kernel command line to boot of a ZFS filesystem.
* Extra options:
* zfsdebug=(on,yes,1) Show extra debugging information
* zfsforce=(on,yes,1) Force import the pool
* rollback=(on,yes,1) Rollback (instead of clone) the snapshot
* Only try to import pool if it haven't already been imported
* This will negate the need to force import a pool that have not been exported cleanly.
* Support exclusion of pools to import by setting ZFS_POOL_EXCEPTIONS in /etc/default/zfs.
* Support additional configuration variable ZFS_INITRD_ADDITIONAL_DATASETS
to mount additional filesystems not located under your root dataset.
* Include /etc/modprobe.d/{zfs,spl}.conf in the initrd if it/they exist.
* Include the udev rule to use by-vdev for pool imports.
* Include the /etc/default/zfs file to the initrd.
* Only try /dev/disk/by-* in the initrd if USE_DISK_BY_ID is set.
* Use /dev/disk/by-vdev before anything.
* Add /dev as a last ditch attempt.
* Fallback to using the cache file if that exist if nothing else worked.
* Use /sbin/modprobe instead of built-in (BusyBox) modprobe.
This gets rid of the message "modprobe: can't load module zcommon".
Thanx to pcoultha for finding this.
Signed-off-by: Turbo Fredriksson <turbo@bayour.com>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #2116
Closes #2114
2014-01-30 20:26:48 +04:00
|
|
|
contrib/initramfs/Makefile
|
2017-11-08 01:53:57 +03:00
|
|
|
contrib/initramfs/hooks/Makefile
|
|
|
|
contrib/initramfs/scripts/Makefile
|
|
|
|
contrib/initramfs/scripts/local-top/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 11:34:45 +03:00
|
|
|
contrib/pyzfs/Makefile
|
2019-01-09 02:56:42 +03:00
|
|
|
contrib/pyzfs/setup.py
|
2019-07-31 02:02:19 +03:00
|
|
|
contrib/zcp/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
module/Makefile
|
|
|
|
module/avl/Makefile
|
|
|
|
module/nvpair/Makefile
|
|
|
|
module/unicode/Makefile
|
|
|
|
module/zcommon/Makefile
|
|
|
|
module/zfs/Makefile
|
2018-02-08 19:16:23 +03:00
|
|
|
module/lua/Makefile
|
2016-05-12 17:51:24 +03:00
|
|
|
module/icp/Makefile
|
2018-02-16 04:53:18 +03:00
|
|
|
module/spl/Makefile
|
2010-09-05 00:26:23 +04:00
|
|
|
include/Makefile
|
2011-01-18 22:42:25 +03:00
|
|
|
include/linux/Makefile
|
2018-02-16 04:53:18 +03:00
|
|
|
include/spl/Makefile
|
|
|
|
include/spl/rpc/Makefile
|
|
|
|
include/spl/sys/Makefile
|
2010-09-05 00:26:23 +04:00
|
|
|
include/sys/Makefile
|
|
|
|
include/sys/fs/Makefile
|
|
|
|
include/sys/fm/Makefile
|
|
|
|
include/sys/fm/fs/Makefile
|
2016-05-12 17:51:24 +03:00
|
|
|
include/sys/crypto/Makefile
|
2016-07-28 01:29:15 +03:00
|
|
|
include/sys/sysevent/Makefile
|
2018-02-08 19:16:23 +03:00
|
|
|
include/sys/lua/Makefile
|
2010-08-26 22:22:58 +04:00
|
|
|
scripts/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/Makefile
|
|
|
|
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 03:26:38 +03:00
|
|
|
tests/test-runner/bin/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/test-runner/include/Makefile
|
|
|
|
tests/test-runner/man/Makefile
|
|
|
|
tests/runfiles/Makefile
|
|
|
|
tests/zfs-tests/Makefile
|
2017-04-12 23:36:48 +03:00
|
|
|
tests/zfs-tests/callbacks/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/cmd/Makefile
|
|
|
|
tests/zfs-tests/cmd/chg_usr_exec/Makefile
|
2018-03-08 02:40:42 +03:00
|
|
|
tests/zfs-tests/cmd/user_ns_exec/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/cmd/devname2devid/Makefile
|
|
|
|
tests/zfs-tests/cmd/dir_rd_update/Makefile
|
|
|
|
tests/zfs-tests/cmd/file_check/Makefile
|
|
|
|
tests/zfs-tests/cmd/file_trunc/Makefile
|
|
|
|
tests/zfs-tests/cmd/file_write/Makefile
|
|
|
|
tests/zfs-tests/cmd/largest_file/Makefile
|
Add basic zfs ioc input nvpair validation
We want newer versions of libzfs_core to run against an existing
zfs kernel module (i.e. a deferred reboot or module reload after
an update).
Programmatically document, via a zfs_ioc_key_t, the valid arguments
for the ioc commands that rely on nvpair input arguments (i.e. non
legacy commands from libzfs_core). Automatically verify the expected
pairs before dispatching a command.
This initial phase focuses on the non-legacy ioctls. A follow-on
change can address the legacy ioctl input from the zfs_cmd_t.
The zfs_ioc_key_t for zfs_keys_channel_program looks like:
static const zfs_ioc_key_t zfs_keys_channel_program[] = {
{"program", DATA_TYPE_STRING, 0},
{"arg", DATA_TYPE_UNKNOWN, 0},
{"sync", DATA_TYPE_BOOLEAN_VALUE, ZK_OPTIONAL},
{"instrlimit", DATA_TYPE_UINT64, ZK_OPTIONAL},
{"memlimit", DATA_TYPE_UINT64, ZK_OPTIONAL},
};
Introduce four input errors to identify specific input failures
(in addition to generic argument value errors like EINVAL, ERANGE,
EBADF, and E2BIG).
ZFS_ERR_IOC_CMD_UNAVAIL the ioctl number is not supported by kernel
ZFS_ERR_IOC_ARG_UNAVAIL an input argument is not supported by kernel
ZFS_ERR_IOC_ARG_REQUIRED a required input argument is missing
ZFS_ERR_IOC_ARG_BADTYPE an input argument has an invalid type
Reviewed-by: Matthew Ahrens <mahrens@delphix.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Don Brady <don.brady@delphix.com>
Closes #7780
2018-09-02 22:14:01 +03:00
|
|
|
tests/zfs-tests/cmd/libzfs_input_check/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/cmd/mkbusy/Makefile
|
|
|
|
tests/zfs-tests/cmd/mkfile/Makefile
|
|
|
|
tests/zfs-tests/cmd/mkfiles/Makefile
|
|
|
|
tests/zfs-tests/cmd/mktree/Makefile
|
|
|
|
tests/zfs-tests/cmd/mmap_exec/Makefile
|
2018-03-28 20:19:22 +03:00
|
|
|
tests/zfs-tests/cmd/mmap_libaio/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/cmd/mmapwrite/Makefile
|
2018-02-08 19:16:23 +03:00
|
|
|
tests/zfs-tests/cmd/nvlist_to_lua/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/cmd/randfree_file/Makefile
|
2016-12-17 01:11:29 +03:00
|
|
|
tests/zfs-tests/cmd/randwritecomp/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/cmd/readmmap/Makefile
|
|
|
|
tests/zfs-tests/cmd/rename_dir/Makefile
|
|
|
|
tests/zfs-tests/cmd/rm_lnkcnt_zero_file/Makefile
|
|
|
|
tests/zfs-tests/cmd/threadsappend/Makefile
|
|
|
|
tests/zfs-tests/cmd/xattrtest/Makefile
|
|
|
|
tests/zfs-tests/include/Makefile
|
|
|
|
tests/zfs-tests/tests/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/acl/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/acl/posix/Makefile
|
2018-01-29 21:24:52 +03:00
|
|
|
tests/zfs-tests/tests/functional/arc/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/atime/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/bootfs/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/cache/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/cachefile/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/casenorm/Makefile
|
2016-06-16 01:47:05 +03:00
|
|
|
tests/zfs-tests/tests/functional/checksum/Makefile
|
2018-02-08 19:16:23 +03: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-17 02:15:48 +03:00
|
|
|
tests/zfs-tests/tests/functional/chattr/Makefile
|
2015-07-02 01:23:09 +03: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
|
2017-09-25 20:32:34 +03: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 20:36:48 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_change-key/Makefile
|
2015-07-02 01:23:09 +03: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 23:04:14 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_diff/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_get/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_inherit/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 20:36:48 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_load-key/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_mount/Makefile
|
2018-03-19 22:40:58 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_program/Makefile
|
2015-07-02 01:23:09 +03: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
|
2018-04-19 19:45:17 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_remap/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
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 22:09:53 +03: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 20:36:48 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zfs_unload-key/Makefile
|
2015-07-02 01:23:09 +03: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
|
|
|
|
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-27 02:49:33 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_events/Makefile
|
2015-07-02 01:23:09 +03: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 19:52:28 +03: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 17:54:59 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_initialize/Makefile
|
2017-01-13 20:25:15 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_labelclear/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool/Makefile
|
|
|
|
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 22:26:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_reopen/Makefile
|
2018-10-19 07:06:18 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_resilver/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_replace/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_scrub/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_set/Makefile
|
2018-04-12 20:57:24 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_split/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_status/Makefile
|
2017-05-19 22:33:11 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_sync/Makefile
|
2019-03-29 19:13:20 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_trim/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_upgrade/Makefile
|
2018-08-15 19:52:28 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_root/zpool_upgrade/blockfiles/Makefile
|
2015-07-02 01:23:09 +03: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 21:21:54 +03:00
|
|
|
tests/zfs-tests/tests/functional/cli_user/zpool_status/Makefile
|
2015-07-02 01:23:09 +03: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-19 00:19:50 +03:00
|
|
|
tests/zfs-tests/tests/functional/cp_files/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/ctime/Makefile
|
2017-12-19 01:06:07 +03:00
|
|
|
tests/zfs-tests/tests/functional/deadman/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/delegate/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/devices/Makefile
|
2017-05-18 22:57:21 +03:00
|
|
|
tests/zfs-tests/tests/functional/events/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/exec/Makefile
|
2016-09-23 23:51:08 +03:00
|
|
|
tests/zfs-tests/tests/functional/fault/Makefile
|
2015-07-02 01:23:09 +03: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 04:25:34 +03:00
|
|
|
tests/zfs-tests/tests/functional/features/large_dnode/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/features/Makefile
|
2018-06-21 00:03:13 +03:00
|
|
|
tests/zfs-tests/tests/functional/grow/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/history/Makefile
|
2017-09-12 23:15:11 +03:00
|
|
|
tests/zfs-tests/tests/functional/hkdf/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/inheritance/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/inuse/Makefile
|
2018-08-27 20:04:21 +03:00
|
|
|
tests/zfs-tests/tests/functional/io/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/large_files/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/largest_pool/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/link_count/Makefile
|
2015-03-11 13:02:08 +03:00
|
|
|
tests/zfs-tests/tests/functional/libzfs/Makefile
|
2019-01-08 21:17:46 +03:00
|
|
|
tests/zfs-tests/tests/functional/limits/Makefile
|
2015-07-02 01:23:09 +03: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 06:20:35 +03:00
|
|
|
tests/zfs-tests/tests/functional/mmp/Makefile
|
2015-07-02 01:23:09 +03: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
|
|
|
|
tests/zfs-tests/tests/functional/pool_names/Makefile
|
2016-12-17 01:11:29 +03:00
|
|
|
tests/zfs-tests/tests/functional/pool_checkpoint/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/poolversion/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/privilege/Makefile
|
2018-09-26 21:08:12 +03:00
|
|
|
tests/zfs-tests/tests/functional/procfs/Makefile
|
2018-02-14 01:54:54 +03: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 11:34:45 +03:00
|
|
|
tests/zfs-tests/tests/functional/pyzfs/Makefile
|
2015-07-02 01:23:09 +03: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 11:04:31 +03:00
|
|
|
tests/zfs-tests/tests/functional/raidz/Makefile
|
2015-07-02 01:23:09 +03: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 19:30:13 +03:00
|
|
|
tests/zfs-tests/tests/functional/removal/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/rename_dirs/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/replacement/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/reservation/Makefile
|
2019-11-27 21:15:01 +03:00
|
|
|
tests/zfs-tests/tests/functional/resilver/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/rootpool/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/rsend/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/scrub_mirror/Makefile
|
|
|
|
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
|
2019-07-26 23:52:30 +03:00
|
|
|
tests/zfs-tests/tests/functional/suid/Makefile
|
2018-09-06 04:33:36 +03:00
|
|
|
tests/zfs-tests/tests/functional/alloc_class/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/threadsappend/Makefile
|
2016-01-26 23:29:46 +03:00
|
|
|
tests/zfs-tests/tests/functional/tmpfile/Makefile
|
2019-03-29 19:13:20 +03:00
|
|
|
tests/zfs-tests/tests/functional/trim/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/truncate/Makefile
|
2018-03-08 02:40:42 +03:00
|
|
|
tests/zfs-tests/tests/functional/user_namespace/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/userquota/Makefile
|
2016-10-04 21:46:10 +03:00
|
|
|
tests/zfs-tests/tests/functional/upgrade/Makefile
|
2016-04-11 23:16:57 +03:00
|
|
|
tests/zfs-tests/tests/functional/vdev_zaps/Makefile
|
2015-07-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/functional/write_dirs/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/xattr/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/zvol/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_cli/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_ENOSPC/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_misc/Makefile
|
|
|
|
tests/zfs-tests/tests/functional/zvol/zvol_swap/Makefile
|
2016-08-04 00:26:15 +03: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-02 01:23:09 +03:00
|
|
|
tests/zfs-tests/tests/stress/Makefile
|
2013-02-18 00:10:17 +04:00
|
|
|
rpm/Makefile
|
2015-03-26 02:59:17 +03:00
|
|
|
rpm/redhat/Makefile
|
|
|
|
rpm/redhat/zfs.spec
|
|
|
|
rpm/redhat/zfs-kmod.spec
|
|
|
|
rpm/redhat/zfs-dkms.spec
|
2013-02-18 00:10:17 +04:00
|
|
|
rpm/generic/Makefile
|
|
|
|
rpm/generic/zfs.spec
|
|
|
|
rpm/generic/zfs-kmod.spec
|
|
|
|
rpm/generic/zfs-dkms.spec
|
2012-07-12 23:21:25 +04:00
|
|
|
zfs.release
|
2010-08-26 22:22:58 +04:00
|
|
|
])
|
|
|
|
|
2016-10-19 22:55:59 +03:00
|
|
|
|
2010-08-26 22:22:58 +04:00
|
|
|
AC_OUTPUT
|