c/mirror_zfs
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_zfs.git synced 2026-05-22 02:27:36 +03:00
Code Issues Packages Projects Releases Wiki Activity

Replace ZoL with OpenZFS where applicable

Browse Source 
Afterward, git grep ZoL matches:
  * README.md:  * [ZoL Site](https://zfsonlinux.org)
  - Correct
  * etc/default/zfs.in:# ZoL userland configuration.
  - Changing this would induce a needless upgrade-check,
    if the user has modified the configuration;
    this can be updated the next time the defaults change
  * module/zfs/dmu_send.c:   * ZoL < 0.7 does not handle [...]
  - Before 0.7 is ZoL, so fair enough

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Issue #11956
This commit is contained in:
наб
2021-05-03 21:21:21 +02:00
committed by Brian Behlendorf
parent cb18cf6b0a
commit b1dd6351bb
26 changed files with 35 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/zfs-tests/tests/functional/atime/root_atime_off.ksh
+1 -1
View File
@@ -53,7 +53,7 @@ log_onexit cleanup
#
# Create $TESTFILE, snapshot and clone.
# Same as 002 except that atime applies to root dataset (ZoL#8675).
# Same as 002 except that atime applies to root dataset (OpenZFS#8675).
#
setup_snap_clone
reset_atime
tests/zfs-tests/tests/functional/atime/root_atime_on.ksh
+1 -1
View File
@@ -52,7 +52,7 @@ log_onexit cleanup
#
# Create $TESTFILE, snapshot and clone.
# Same as 001 except that atime/relatime applies to root dataset (ZoL#8675).
# Same as 001 except that atime/relatime applies to root dataset (OpenZFS#8675).
#
setup_snap_clone
reset_atime
tests/zfs-tests/tests/functional/atime/root_relatime_on.ksh
+1 -1
View File
@@ -53,7 +53,7 @@ log_onexit cleanup
#
# Create $TESTFILE, snapshot and clone.
# Same as 003 except that atime/relatime applies to root dataset (ZoL#8675).
# Same as 003 except that atime/relatime applies to root dataset (OpenZFS#8675).
#
setup_snap_clone
reset_atime
tests/zfs-tests/tests/functional/cli_root/zfs_mount/zfs_mount_test_race.ksh
+5 -4
View File
@@ -87,10 +87,11 @@ log_must zfs set mountpoint=$MNTPT $TESTPOOL2
# At this point, layout of datasets in two pools will look like below.
# Previously, on next `zfs mount -a`, pthreads assigned to TESTFS1 and TESTFS2
# could race, and TESTFS2 usually (actually always) won in ZoL. Note that the
# problem is how two or more threads could initially be assigned to the same
# top level directory, not this specific layout. This layout is just an example
# that can reproduce race, and is also the layout reported in #8833.
# could race, and TESTFS2 usually (actually always) won in OpenZFS.
# Note that the problem is how two or more threads could initially be assigned
# to the same top level directory, not this specific layout.
# This layout is just an example that can reproduce race,
# and is also the layout reported in #8833.
#
# NAME MOUNTED MOUNTPOINT
# ----------------------------------------------
tests/zfs-tests/tests/functional/rsend/send_encrypted_files.ksh
+1 -1
View File
@@ -84,7 +84,7 @@ log_must mkdir -p /$TESTPOOL/$TESTFS2/xattrsadir
log_must zfs set xattr=sa $TESTPOOL/$TESTFS2
log_must xattrtest -f 10 -x 3 -s 32768 -r -k -p /$TESTPOOL/$TESTFS2/xattrsadir
# ZoL issue #7432
# OpenZFS issue #7432
log_must zfs set compression=on xattr=sa $TESTPOOL/$TESTFS2
log_must touch /$TESTPOOL/$TESTFS2/attrs
log_must eval "python -c 'print \"a\" * 4096' | \