2025-01-04 03:04:27 +03:00
|
|
|
// SPDX-License-Identifier: CDDL-1.0
|
2008-12-11 22:14:49 +03:00
|
|
|
/*
|
|
|
|
|
* CDDL HEADER START
|
|
|
|
|
*
|
|
|
|
|
* The contents of this file are subject to the terms of the
|
|
|
|
|
* Common Development and Distribution License (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
|
2022-07-12 00:16:13 +03:00
|
|
|
* or https://opensource.org/licenses/CDDL-1.0.
|
2008-12-11 22:14:49 +03:00
|
|
|
* 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
|
|
|
|
|
*/
|
|
|
|
|
/*
|
2017-01-31 21:13:10 +03:00
|
|
|
* Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved.
|
|
|
|
|
* Copyright 2011 Nexenta Systems, Inc. All rights reserved.
|
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 19:48:13 +03:00
|
|
|
* Copyright (c) 2012, 2018 by Delphix. All rights reserved.
|
2012-05-10 02:05:14 +04:00
|
|
|
* Copyright (c) 2012, Joyent, Inc. All rights reserved.
|
2011-11-08 04:26:52 +04:00
|
|
|
*/
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
#ifndef _SYS_ZFS_CONTEXT_H
|
|
|
|
|
#define _SYS_ZFS_CONTEXT_H
|
|
|
|
|
|
2020-06-06 22:54:04 +03:00
|
|
|
#ifdef __cplusplus
|
|
|
|
|
extern "C" {
|
|
|
|
|
#endif
|
|
|
|
|
|
2020-10-14 07:05:49 +03:00
|
|
|
/*
|
|
|
|
|
* This code compiles in three different contexts. When __KERNEL__ is defined,
|
|
|
|
|
* the code uses "unix-like" kernel interfaces. When _STANDALONE is defined, the
|
|
|
|
|
* code is running in a reduced capacity environment of the boot loader which is
|
|
|
|
|
* generally a subset of both POSIX and kernel interfaces (with a few unique
|
|
|
|
|
* interfaces too). When neither are defined, it's in a userland POSIX or
|
|
|
|
|
* similar environment.
|
|
|
|
|
*/
|
|
|
|
|
#if defined(__KERNEL__) || defined(_STANDALONE)
|
2010-09-05 00:26:23 +04:00
|
|
|
#include <sys/types.h>
|
|
|
|
|
#include <sys/atomic.h>
|
|
|
|
|
#include <sys/sysmacros.h>
|
2018-02-16 04:53:18 +03:00
|
|
|
#include <sys/vmsystm.h>
|
|
|
|
|
#include <sys/condvar.h>
|
2010-09-05 00:26:23 +04:00
|
|
|
#include <sys/cmn_err.h>
|
|
|
|
|
#include <sys/kmem.h>
|
2014-12-09 03:03:50 +03:00
|
|
|
#include <sys/kmem_cache.h>
|
2014-12-03 22:56:32 +03:00
|
|
|
#include <sys/vmem.h>
|
2022-09-28 19:48:46 +03:00
|
|
|
#include <sys/misc.h>
|
2010-09-05 00:26:23 +04:00
|
|
|
#include <sys/taskq.h>
|
|
|
|
|
#include <sys/param.h>
|
|
|
|
|
#include <sys/disp.h>
|
|
|
|
|
#include <sys/debug.h>
|
|
|
|
|
#include <sys/random.h>
|
2022-01-22 03:56:46 +03:00
|
|
|
#include <sys/string.h>
|
2010-09-05 00:26:23 +04:00
|
|
|
#include <sys/byteorder.h>
|
|
|
|
|
#include <sys/list.h>
|
|
|
|
|
#include <sys/time.h>
|
|
|
|
|
#include <sys/zone.h>
|
2016-05-12 17:51:24 +03:00
|
|
|
#include <sys/kstat.h>
|
2010-09-05 00:26:23 +04:00
|
|
|
#include <sys/zfs_debug.h>
|
2016-07-28 01:29:15 +03:00
|
|
|
#include <sys/sysevent.h>
|
|
|
|
|
#include <sys/sysevent/eventdefs.h>
|
Illumos #4045 write throttle & i/o scheduler performance work
4045 zfs write throttle & i/o scheduler performance work
1. The ZFS i/o scheduler (vdev_queue.c) now divides i/os into 5 classes: sync
read, sync write, async read, async write, and scrub/resilver. The scheduler
issues a number of concurrent i/os from each class to the device. Once a class
has been selected, an i/o is selected from this class using either an elevator
algorithem (async, scrub classes) or FIFO (sync classes). The number of
concurrent async write i/os is tuned dynamically based on i/o load, to achieve
good sync i/o latency when there is not a high load of writes, and good write
throughput when there is. See the block comment in vdev_queue.c (reproduced
below) for more details.
2. The write throttle (dsl_pool_tempreserve_space() and
txg_constrain_throughput()) is rewritten to produce much more consistent delays
when under constant load. The new write throttle is based on the amount of
dirty data, rather than guesses about future performance of the system. When
there is a lot of dirty data, each transaction (e.g. write() syscall) will be
delayed by the same small amount. This eliminates the "brick wall of wait"
that the old write throttle could hit, causing all transactions to wait several
seconds until the next txg opens. One of the keys to the new write throttle is
decrementing the amount of dirty data as i/o completes, rather than at the end
of spa_sync(). Note that the write throttle is only applied once the i/o
scheduler is issuing the maximum number of outstanding async writes. See the
block comments in dsl_pool.c and above dmu_tx_delay() (reproduced below) for
more details.
This diff has several other effects, including:
* the commonly-tuned global variable zfs_vdev_max_pending has been removed;
use per-class zfs_vdev_*_max_active values or zfs_vdev_max_active instead.
* the size of each txg (meaning the amount of dirty data written, and thus the
time it takes to write out) is now controlled differently. There is no longer
an explicit time goal; the primary determinant is amount of dirty data.
Systems that are under light or medium load will now often see that a txg is
always syncing, but the impact to performance (e.g. read latency) is minimal.
Tune zfs_dirty_data_max and zfs_dirty_data_sync to control this.
* zio_taskq_batch_pct = 75 -- Only use 75% of all CPUs for compression,
checksum, etc. This improves latency by not allowing these CPU-intensive tasks
to consume all CPU (on machines with at least 4 CPU's; the percentage is
rounded up).
--matt
APPENDIX: problems with the current i/o scheduler
The current ZFS i/o scheduler (vdev_queue.c) is deadline based. The problem
with this is that if there are always i/os pending, then certain classes of
i/os can see very long delays.
For example, if there are always synchronous reads outstanding, then no async
writes will be serviced until they become "past due". One symptom of this
situation is that each pass of the txg sync takes at least several seconds
(typically 3 seconds).
If many i/os become "past due" (their deadline is in the past), then we must
service all of these overdue i/os before any new i/os. This happens when we
enqueue a batch of async writes for the txg sync, with deadlines 2.5 seconds in
the future. If we can't complete all the i/os in 2.5 seconds (e.g. because
there were always reads pending), then these i/os will become past due. Now we
must service all the "async" writes (which could be hundreds of megabytes)
before we service any reads, introducing considerable latency to synchronous
i/os (reads or ZIL writes).
Notes on porting to ZFS on Linux:
- zio_t gained new members io_physdone and io_phys_children. Because
object caches in the Linux port call the constructor only once at
allocation time, objects may contain residual data when retrieved
from the cache. Therefore zio_create() was updated to zero out the two
new fields.
- vdev_mirror_pending() relied on the depth of the per-vdev pending queue
(vq->vq_pending_tree) to select the least-busy leaf vdev to read from.
This tree has been replaced by vq->vq_active_tree which is now used
for the same purpose.
- vdev_queue_init() used the value of zfs_vdev_max_pending to determine
the number of vdev I/O buffers to pre-allocate. That global no longer
exists, so we instead use the sum of the *_max_active values for each of
the five I/O classes described above.
- The Illumos implementation of dmu_tx_delay() delays a transaction by
sleeping in condition variable embedded in the thread
(curthread->t_delay_cv). We do not have an equivalent CV to use in
Linux, so this change replaced the delay logic with a wrapper called
zfs_sleep_until(). This wrapper could be adopted upstream and in other
downstream ports to abstract away operating system-specific delay logic.
- These tunables are added as module parameters, and descriptions added
to the zfs-module-parameters.5 man page.
spa_asize_inflation
zfs_deadman_synctime_ms
zfs_vdev_max_active
zfs_vdev_async_write_active_min_dirty_percent
zfs_vdev_async_write_active_max_dirty_percent
zfs_vdev_async_read_max_active
zfs_vdev_async_read_min_active
zfs_vdev_async_write_max_active
zfs_vdev_async_write_min_active
zfs_vdev_scrub_max_active
zfs_vdev_scrub_min_active
zfs_vdev_sync_read_max_active
zfs_vdev_sync_read_min_active
zfs_vdev_sync_write_max_active
zfs_vdev_sync_write_min_active
zfs_dirty_data_max_percent
zfs_delay_min_dirty_percent
zfs_dirty_data_max_max_percent
zfs_dirty_data_max
zfs_dirty_data_max_max
zfs_dirty_data_sync
zfs_delay_scale
The latter four have type unsigned long, whereas they are uint64_t in
Illumos. This accommodates Linux's module_param() supported types, but
means they may overflow on 32-bit architectures.
The values zfs_dirty_data_max and zfs_dirty_data_max_max are the most
likely to overflow on 32-bit systems, since they express physical RAM
sizes in bytes. In fact, Illumos initializes zfs_dirty_data_max_max to
2^32 which does overflow. To resolve that, this port instead initializes
it in arc_init() to 25% of physical RAM, and adds the tunable
zfs_dirty_data_max_max_percent to override that percentage. While this
solution doesn't completely avoid the overflow issue, it should be a
reasonable default for most systems, and the minority of affected
systems can work around the issue by overriding the defaults.
- Fixed reversed logic in comment above zfs_delay_scale declaration.
- Clarified comments in vdev_queue.c regarding when per-queue minimums take
effect.
- Replaced dmu_tx_write_limit in the dmu_tx kstat file
with dmu_tx_dirty_delay and dmu_tx_dirty_over_max. The first counts
how many times a transaction has been delayed because the pool dirty
data has exceeded zfs_delay_min_dirty_percent. The latter counts how
many times the pool dirty data has exceeded zfs_dirty_data_max (which
we expect to never happen).
- The original patch would have regressed the bug fixed in
zfsonlinux/zfs@c418410, which prevented users from setting the
zfs_vdev_aggregation_limit tuning larger than SPA_MAXBLOCKSIZE.
A similar fix is added to vdev_queue_aggregate().
- In vdev_queue_io_to_issue(), dynamically allocate 'zio_t search' on the
heap instead of the stack. In Linux we can't afford such large
structures on the stack.
Reviewed by: George Wilson <george.wilson@delphix.com>
Reviewed by: Adam Leventhal <ahl@delphix.com>
Reviewed by: Christopher Siden <christopher.siden@delphix.com>
Reviewed by: Ned Bass <bass6@llnl.gov>
Reviewed by: Brendan Gregg <brendan.gregg@joyent.com>
Approved by: Robert Mustacchi <rm@joyent.com>
References:
http://www.illumos.org/issues/4045
illumos/illumos-gate@69962b5647e4a8b9b14998733b765925381b727e
Ported-by: Ned Bass <bass6@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #1913
2013-08-29 07:01:20 +04:00
|
|
|
#include <sys/zfs_delay.h>
|
2010-09-05 00:26:23 +04:00
|
|
|
#include <sys/sunddi.h>
|
2011-11-15 23:01:27 +04:00
|
|
|
#include <sys/ctype.h>
|
2012-08-24 04:45:31 +04:00
|
|
|
#include <sys/disp.h>
|
Swap DTRACE_PROBE* with Linux tracepoints
This patch leverages Linux tracepoints from within the ZFS on Linux
code base. It also refactors the debug code to bring it back in sync
with Illumos.
The information exported via tracepoints can be used for a variety of
reasons (e.g. debugging, tuning, general exploration/understanding,
etc). It is advantageous to use Linux tracepoints as the mechanism to
export this kind of information (as opposed to something else) for a
number of reasons:
* A number of external tools can make use of our tracepoints
"automatically" (e.g. perf, systemtap)
* Tracepoints are designed to be extremely cheap when disabled
* It's one of the "accepted" ways to export this kind of
information; many other kernel subsystems use tracepoints too.
Unfortunately, though, there are a few caveats as well:
* Linux tracepoints appear to only be available to GPL licensed
modules due to the way certain kernel functions are exported.
Thus, to actually make use of the tracepoints introduced by this
patch, one might have to patch and re-compile the kernel;
exporting the necessary functions to non-GPL modules.
* Prior to upstream kernel version v3.14-rc6-30-g66cc69e, Linux
tracepoints are not available for unsigned kernel modules
(tracepoints will get disabled due to the module's 'F' taint).
Thus, one either has to sign the zfs kernel module prior to
loading it, or use a kernel versioned v3.14-rc6-30-g66cc69e or
newer.
Assuming the above two requirements are satisfied, lets look at an
example of how this patch can be used and what information it exposes
(all commands run as 'root'):
# list all zfs tracepoints available
$ ls /sys/kernel/debug/tracing/events/zfs
enable filter zfs_arc__delete
zfs_arc__evict zfs_arc__hit zfs_arc__miss
zfs_l2arc__evict zfs_l2arc__hit zfs_l2arc__iodone
zfs_l2arc__miss zfs_l2arc__read zfs_l2arc__write
zfs_new_state__mfu zfs_new_state__mru
# enable all zfs tracepoints, clear the tracepoint ring buffer
$ echo 1 > /sys/kernel/debug/tracing/events/zfs/enable
$ echo 0 > /sys/kernel/debug/tracing/trace
# import zpool called 'tank', inspect tracepoint data (each line was
# truncated, they're too long for a commit message otherwise)
$ zpool import tank
$ cat /sys/kernel/debug/tracing/trace | head -n35
# tracer: nop
#
# entries-in-buffer/entries-written: 1219/1219 #P:8
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
lt-zpool-30132 [003] .... 91344.200050: zfs_arc__miss: hdr...
z_rd_int/0-30156 [003] .... 91344.200611: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.201173: zfs_arc__miss: hdr...
z_rd_int/1-30157 [003] .... 91344.201756: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.201795: zfs_arc__miss: hdr...
z_rd_int/2-30158 [003] .... 91344.202099: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.202126: zfs_arc__hit: hdr ...
lt-zpool-30132 [003] .... 91344.202130: zfs_arc__hit: hdr ...
lt-zpool-30132 [003] .... 91344.202134: zfs_arc__hit: hdr ...
lt-zpool-30132 [003] .... 91344.202146: zfs_arc__miss: hdr...
z_rd_int/3-30159 [003] .... 91344.202457: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.202484: zfs_arc__miss: hdr...
z_rd_int/4-30160 [003] .... 91344.202866: zfs_new_state__mru...
lt-zpool-30132 [003] .... 91344.202891: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.203034: zfs_arc__miss: hdr...
z_rd_iss/1-30149 [001] .... 91344.203749: zfs_new_state__mru...
lt-zpool-30132 [001] .... 91344.203789: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.203878: zfs_arc__miss: hdr...
z_rd_iss/3-30151 [001] .... 91344.204315: zfs_new_state__mru...
lt-zpool-30132 [001] .... 91344.204332: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204337: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204352: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204356: zfs_arc__hit: hdr ...
lt-zpool-30132 [001] .... 91344.204360: zfs_arc__hit: hdr ...
To highlight the kind of detailed information that is being exported
using this infrastructure, I've taken the first tracepoint line from the
output above and reformatted it such that it fits in 80 columns:
lt-zpool-30132 [003] .... 91344.200050: zfs_arc__miss:
hdr {
dva 0x1:0x40082
birth 15491
cksum0 0x163edbff3a
flags 0x640
datacnt 1
type 1
size 2048
spa 3133524293419867460
state_type 0
access 0
mru_hits 0
mru_ghost_hits 0
mfu_hits 0
mfu_ghost_hits 0
l2_hits 0
refcount 1
} bp {
dva0 0x1:0x40082
dva1 0x1:0x3000e5
dva2 0x1:0x5a006e
cksum 0x163edbff3a:0x75af30b3dd6:0x1499263ff5f2b:0x288bd118815e00
lsize 2048
} zb {
objset 0
object 0
level -1
blkid 0
}
For the specific tracepoint shown here, 'zfs_arc__miss', data is
exported detailing the arc_buf_hdr_t (hdr), blkptr_t (bp), and
zbookmark_t (zb) that caused the ARC miss (down to the exact DVA!).
This kind of precise and detailed information can be extremely valuable
when trying to answer certain kinds of questions.
For anybody unfamiliar but looking to build on this, I found the XFS
source code along with the following three web links to be extremely
helpful:
* http://lwn.net/Articles/379903/
* http://lwn.net/Articles/381064/
* http://lwn.net/Articles/383362/
I should also node the more "boring" aspects of this patch:
* The ZFS_LINUX_COMPILE_IFELSE autoconf macro was modified to
support a sixth paramter. This parameter is used to populate the
contents of the new conftest.h file. If no sixth parameter is
provided, conftest.h will be empty.
* The ZFS_LINUX_TRY_COMPILE_HEADER autoconf macro was introduced.
This macro is nearly identical to the ZFS_LINUX_TRY_COMPILE macro,
except it has support for a fifth option that is then passed as
the sixth parameter to ZFS_LINUX_COMPILE_IFELSE.
These autoconf changes were needed to test the availability of the Linux
tracepoint macros. Due to the odd nature of the Linux tracepoint macro
API, a separate ".h" must be created (the path and filename is used
internally by the kernel's define_trace.h file).
* The HAVE_DECLARE_EVENT_CLASS autoconf macro was introduced. This
is to determine if we can safely enable the Linux tracepoint
functionality. We need to selectively disable the tracepoint code
due to the kernel exporting certain functions as GPL only. Without
this check, the build process will fail at link time.
In addition, the SET_ERROR macro was modified into a tracepoint as well.
To do this, the 'sdt.h' file was moved into the 'include/sys' directory
and now contains a userspace portion and a kernel space portion. The
dprintf and zfs_dbgmsg* interfaces are now implemented as tracepoint as
well.
Signed-off-by: Prakash Surya <surya1@llnl.gov>
Signed-off-by: Ned Bass <bass6@llnl.gov>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2014-06-13 21:54:48 +04:00
|
|
|
#include <sys/trace.h>
|
2018-09-26 21:08:12 +03:00
|
|
|
#include <sys/procfs_list.h>
|
2019-11-01 20:41:03 +03:00
|
|
|
#include <sys/mod.h>
|
2021-02-21 07:16:50 +03:00
|
|
|
#include <sys/uio_impl.h>
|
2019-12-05 00:12:57 +03:00
|
|
|
#include <sys/zfs_context_os.h>
|
2020-10-14 07:05:49 +03:00
|
|
|
#else /* _KERNEL || _STANDALONE */
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
#define _SYS_VFS_H
|
|
|
|
|
#define _SYS_SUNDDI_H
|
|
|
|
|
#define _SYS_CALLB_H
|
|
|
|
|
|
|
|
|
|
#include <stdio.h>
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
#include <stddef.h>
|
|
|
|
|
#include <stdarg.h>
|
|
|
|
|
#include <fcntl.h>
|
|
|
|
|
#include <unistd.h>
|
|
|
|
|
#include <errno.h>
|
|
|
|
|
#include <string.h>
|
2018-02-08 19:16:23 +03:00
|
|
|
#include <setjmp.h>
|
2008-12-11 22:14:49 +03:00
|
|
|
#include <assert.h>
|
|
|
|
|
#include <limits.h>
|
|
|
|
|
#include <atomic.h>
|
|
|
|
|
#include <dirent.h>
|
|
|
|
|
#include <time.h>
|
2011-11-15 23:01:27 +04:00
|
|
|
#include <ctype.h>
|
2013-05-17 01:18:06 +04:00
|
|
|
#include <signal.h>
|
|
|
|
|
#include <sys/mman.h>
|
2008-12-11 22:14:49 +03:00
|
|
|
#include <sys/types.h>
|
|
|
|
|
#include <sys/cred.h>
|
|
|
|
|
#include <sys/sysmacros.h>
|
|
|
|
|
#include <sys/resource.h>
|
|
|
|
|
#include <sys/byteorder.h>
|
|
|
|
|
#include <sys/list.h>
|
2019-11-01 20:41:03 +03:00
|
|
|
#include <sys/mod.h>
|
2008-12-11 22:14:49 +03:00
|
|
|
#include <sys/uio.h>
|
|
|
|
|
#include <sys/zfs_debug.h>
|
|
|
|
|
#include <sys/kstat.h>
|
|
|
|
|
#include <sys/u8_textprep.h>
|
2016-07-28 01:29:15 +03:00
|
|
|
#include <sys/sysevent.h>
|
|
|
|
|
#include <sys/sysevent/eventdefs.h>
|
2010-05-29 00:45:14 +04:00
|
|
|
#include <sys/sunddi.h>
|
2013-05-11 01:17:03 +04:00
|
|
|
#include <sys/debug.h>
|
2014-10-01 23:02:12 +04:00
|
|
|
#include <sys/utsname.h>
|
Enable use of DTRACE_PROBE* macros in "spl" module
This change modifies some of the infrastructure for enabling the use of
the DTRACE_PROBE* macros, such that we can use tehm in the "spl" module.
Currently, when the DTRACE_PROBE* macros are used, they get expanded to
create new functions, and these dynamically generated functions become
part of the "zfs" module.
Since the "spl" module does not depend on the "zfs" module, the use of
DTRACE_PROBE* in the "spl" module would result in undefined symbols
being used in the "spl" module. Specifically, DTRACE_PROBE* would turn
into a function call, and the function being called would be a symbol
only contained in the "zfs" module; which results in a linker and/or
runtime error.
Thus, this change adds the necessary logic to the "spl" module, to
mirror the tracing functionality available to the "zfs" module. After
this change, we'll have a "trace_zfs.h" header file which defines the
probes available only to the "zfs" module, and a "trace_spl.h" header
file which defines the probes available only to the "spl" module.
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-30 21:02:41 +03:00
|
|
|
#include <sys/trace_zfs.h>
|
2008-12-11 22:14:49 +03:00
|
|
|
|
2025-08-09 02:51:43 +03:00
|
|
|
#include <sys/mutex.h>
|
2025-08-09 02:51:43 +03:00
|
|
|
#include <sys/rwlock.h>
|
2025-08-09 02:51:43 +03:00
|
|
|
#include <sys/condvar.h>
|
2025-08-09 03:44:05 +03:00
|
|
|
#include <sys/cmn_err.h>
|
2025-08-25 14:45:35 +03:00
|
|
|
#include <sys/thread.h>
|
2025-08-16 13:23:25 +03:00
|
|
|
#include <sys/taskq.h>
|
2025-10-15 09:31:31 +03:00
|
|
|
#include <sys/tsd.h>
|
2025-10-16 05:12:30 +03:00
|
|
|
#include <sys/procfs_list.h>
|
2025-10-16 05:27:43 +03:00
|
|
|
#include <sys/kmem.h>
|
2025-10-16 05:52:57 +03:00
|
|
|
#include <sys/zfs_delay.h>
|
2025-10-17 14:25:23 +03:00
|
|
|
#include <sys/vnode.h>
|
2025-10-16 05:52:57 +03:00
|
|
|
|
2019-12-05 00:12:57 +03:00
|
|
|
#include <sys/zfs_context_os.h>
|
|
|
|
|
|
2010-08-26 21:58:36 +04:00
|
|
|
/*
|
|
|
|
|
* Stack
|
|
|
|
|
*/
|
|
|
|
|
|
2013-03-08 22:41:28 +04:00
|
|
|
#define noinline __attribute__((noinline))
|
2016-08-27 21:12:53 +03:00
|
|
|
#define likely(x) __builtin_expect((x), 1)
|
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 19:48:13 +03:00
|
|
|
#define unlikely(x) __builtin_expect((x), 0)
|
2010-08-26 21:58:36 +04:00
|
|
|
|
2008-12-11 22:14:49 +03:00
|
|
|
/*
|
|
|
|
|
* DTrace SDT probes have different signatures in userland than they do in
|
2015-12-22 04:31:57 +03:00
|
|
|
* the kernel. If they're being used in kernel code, re-define them out of
|
2008-12-11 22:14:49 +03:00
|
|
|
* existence for their counterparts in libzpool.
|
2015-12-22 04:31:57 +03:00
|
|
|
*
|
|
|
|
|
* Here's an example of how to use the set-error probes in userland:
|
|
|
|
|
* zfs$target:::set-error /arg0 == EBUSY/ {stack();}
|
|
|
|
|
*
|
|
|
|
|
* Here's an example of how to use DTRACE_PROBE probes in userland:
|
|
|
|
|
* If there is a probe declared as follows:
|
|
|
|
|
* DTRACE_PROBE2(zfs__probe_name, uint64_t, blkid, dnode_t *, dn);
|
|
|
|
|
* Then you can use it as follows:
|
|
|
|
|
* zfs$target:::probe2 /copyinstr(arg0) == "zfs__probe_name"/
|
|
|
|
|
* {printf("%u %p\n", arg1, arg2);}
|
2008-12-11 22:14:49 +03:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifdef DTRACE_PROBE
|
|
|
|
|
#undef DTRACE_PROBE
|
|
|
|
|
#endif /* DTRACE_PROBE */
|
2019-10-25 23:38:37 +03:00
|
|
|
#define DTRACE_PROBE(a)
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
#ifdef DTRACE_PROBE1
|
|
|
|
|
#undef DTRACE_PROBE1
|
|
|
|
|
#endif /* DTRACE_PROBE1 */
|
2019-10-25 23:38:37 +03:00
|
|
|
#define DTRACE_PROBE1(a, b, c)
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
#ifdef DTRACE_PROBE2
|
|
|
|
|
#undef DTRACE_PROBE2
|
|
|
|
|
#endif /* DTRACE_PROBE2 */
|
2019-10-25 23:38:37 +03:00
|
|
|
#define DTRACE_PROBE2(a, b, c, d, e)
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
#ifdef DTRACE_PROBE3
|
|
|
|
|
#undef DTRACE_PROBE3
|
|
|
|
|
#endif /* DTRACE_PROBE3 */
|
2019-10-25 23:38:37 +03:00
|
|
|
#define DTRACE_PROBE3(a, b, c, d, e, f, g)
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
#ifdef DTRACE_PROBE4
|
|
|
|
|
#undef DTRACE_PROBE4
|
|
|
|
|
#endif /* DTRACE_PROBE4 */
|
2019-10-25 23:38:37 +03:00
|
|
|
#define DTRACE_PROBE4(a, b, c, d, e, f, g, h, i)
|
2008-12-11 22:14:49 +03:00
|
|
|
|
2020-07-26 06:09:50 +03:00
|
|
|
#ifdef __FreeBSD__
|
|
|
|
|
typedef off_t loff_t;
|
|
|
|
|
#endif
|
2013-09-04 16:00:57 +04:00
|
|
|
|
2016-01-01 16:42:58 +03:00
|
|
|
extern char *vn_dumpdir;
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Random stuff
|
|
|
|
|
*/
|
|
|
|
|
#define max_ncpus 64
|
2015-06-26 21:28:18 +03:00
|
|
|
#define boot_ncpus (sysconf(_SC_NPROCESSORS_ONLN))
|
2008-12-11 22:14:49 +03:00
|
|
|
|
2015-07-24 20:08:31 +03:00
|
|
|
/*
|
|
|
|
|
* Process priorities as defined by setpriority(2) and getpriority(2).
|
|
|
|
|
*/
|
|
|
|
|
#define minclsyspri 19
|
|
|
|
|
#define defclsyspri 0
|
2025-06-30 17:24:23 +03:00
|
|
|
/* Write issue taskq priority. */
|
|
|
|
|
#define wtqclsyspri -19
|
|
|
|
|
#define maxclsyspri -20
|
2008-12-11 22:14:49 +03:00
|
|
|
|
2016-03-01 17:32:52 +03:00
|
|
|
#define CPU_SEQID ((uintptr_t)pthread_self() & (max_ncpus - 1))
|
2020-11-02 22:51:12 +03:00
|
|
|
#define CPU_SEQID_UNSTABLE CPU_SEQID
|
2008-12-11 22:14:49 +03:00
|
|
|
|
2017-06-13 12:16:45 +03:00
|
|
|
#define NN_DIVISOR_1000 (1U << 0)
|
|
|
|
|
#define NN_NUMBUF_SZ (6)
|
|
|
|
|
|
2008-12-11 22:14:49 +03:00
|
|
|
extern uint64_t physmem;
|
2021-04-08 23:17:38 +03:00
|
|
|
extern const char *random_path;
|
|
|
|
|
extern const char *urandom_path;
|
2008-12-11 22:14:49 +03:00
|
|
|
|
2014-04-16 07:40:22 +04:00
|
|
|
extern int highbit64(uint64_t i);
|
2016-02-29 21:05:23 +03:00
|
|
|
extern int lowbit64(uint64_t i);
|
2008-12-11 22:14:49 +03:00
|
|
|
extern int random_get_bytes(uint8_t *ptr, size_t len);
|
|
|
|
|
extern int random_get_pseudo_bytes(uint8_t *ptr, size_t len);
|
|
|
|
|
|
2021-06-23 02:35:23 +03:00
|
|
|
static __inline__ uint32_t
|
|
|
|
|
random_in_range(uint32_t range)
|
|
|
|
|
{
|
|
|
|
|
uint32_t r;
|
|
|
|
|
|
|
|
|
|
ASSERT(range != 0);
|
|
|
|
|
|
|
|
|
|
if (range == 1)
|
|
|
|
|
return (0);
|
|
|
|
|
|
2021-06-25 20:28:51 +03:00
|
|
|
(void) random_get_pseudo_bytes((uint8_t *)&r, sizeof (r));
|
2021-06-23 02:35:23 +03:00
|
|
|
|
|
|
|
|
return (r % range);
|
|
|
|
|
}
|
|
|
|
|
|
2016-05-12 17:51:24 +03:00
|
|
|
extern void random_init(void);
|
|
|
|
|
extern void random_fini(void);
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
typedef struct callb_cpr {
|
|
|
|
|
kmutex_t *cc_lockp;
|
|
|
|
|
} callb_cpr_t;
|
|
|
|
|
|
|
|
|
|
#define CALLB_CPR_INIT(cp, lockp, func, name) { \
|
|
|
|
|
(cp)->cc_lockp = lockp; \
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#define CALLB_CPR_SAFE_BEGIN(cp) { \
|
|
|
|
|
ASSERT(MUTEX_HELD((cp)->cc_lockp)); \
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#define CALLB_CPR_SAFE_END(cp, lockp) { \
|
|
|
|
|
ASSERT(MUTEX_HELD((cp)->cc_lockp)); \
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#define CALLB_CPR_EXIT(cp) { \
|
|
|
|
|
ASSERT(MUTEX_HELD((cp)->cc_lockp)); \
|
|
|
|
|
mutex_exit((cp)->cc_lockp); \
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#define zone_dataset_visible(x, y) (1)
|
|
|
|
|
#define INGLOBALZONE(z) (1)
|
OpenZFS 9075 - Improve ZFS pool import/load process and corrupted pool recovery
Some work has been done lately to improve the debugability of the ZFS pool
load (and import) process. This includes:
7638 Refactor spa_load_impl into several functions
8961 SPA load/import should tell us why it failed
7277 zdb should be able to print zfs_dbgmsg's
To iterate on top of that, there's a few changes that were made to make the
import process more resilient and crash free. One of the first tasks during the
pool load process is to parse a config provided from userland that describes
what devices the pool is composed of. A vdev tree is generated from that config,
and then all the vdevs are opened.
The Meta Object Set (MOS) of the pool is accessed, and several metadata objects
that are necessary to load the pool are read. The exact configuration of the
pool is also stored inside the MOS. Since the configuration provided from
userland is external and might not accurately describe the vdev tree
of the pool at the txg that is being loaded, it cannot be relied upon to safely
operate the pool. For that reason, the configuration in the MOS is read early
on. In the past, the two configurations were compared together and if there was
a mismatch then the load process was aborted and an error was returned.
The latter was a good way to ensure a pool does not get corrupted, however it
made the pool load process needlessly fragile in cases where the vdev
configuration changed or the userland configuration was outdated. Since the MOS
is stored in 3 copies, the configuration provided by userland doesn't have to be
perfect in order to read its contents. Hence, a new approach has been adopted:
The pool is first opened with the untrusted userland configuration just so that
the real configuration can be read from the MOS. The trusted MOS configuration
is then used to generate a new vdev tree and the pool is re-opened.
When the pool is opened with an untrusted configuration, writes are disabled
to avoid accidentally damaging it. During reads, some sanity checks are
performed on block pointers to see if each DVA points to a known vdev;
when the configuration is untrusted, instead of panicking the system if those
checks fail we simply avoid issuing reads to the invalid DVAs.
This new two-step pool load process now allows rewinding pools accross
vdev tree changes such as device replacement, addition, etc. Loading a pool
from an external config file in a clustering environment also becomes much
safer now since the pool will import even if the config is outdated and didn't,
for instance, register a recent device addition.
With this code in place, it became relatively easy to implement a
long-sought-after feature: the ability to import a pool with missing top level
(i.e. non-redundant) devices. Note that since this almost guarantees some loss
of data, this feature is for now restricted to a read-only import.
Porting notes (ZTS):
* Fix 'make dist' target in zpool_import
* The maximum path length allowed by tar is 99 characters. Several
of the new test cases exceeded this limit resulting in them not
being included in the tarball. Shorten the names slightly.
* Set/get tunables using accessor functions.
* Get last synced txg via the "zfs_txg_history" mechanism.
* Clear zinject handlers in cleanup for import_cache_device_replaced
and import_rewind_device_replaced in order that the zpool can be
exported if there is an error.
* Increase FILESIZE to 8G in zfs-test.sh to allow for a larger
ext4 file system to be created on ZFS_DISK2. Also, there's
no need to partition ZFS_DISK2 at all. The partitioning had
already been disabled for multipath devices. Among other things,
the partitioning steals some space from the ext4 file system,
makes it difficult to accurately calculate the paramters to
parted and can make some of the tests fail.
* Increase FS_SIZE and FILE_SIZE in the zpool_import test
configuration now that FILESIZE is larger.
* Write more data in order that device evacuation take lonnger in
a couple tests.
* Use mkdir -p to avoid errors when the directory already exists.
* Remove use of sudo in import_rewind_config_changed.
Authored by: Pavel Zakharov <pavel.zakharov@delphix.com>
Reviewed by: George Wilson <george.wilson@delphix.com>
Reviewed by: Matthew Ahrens <mahrens@delphix.com>
Reviewed by: Andrew Stormont <andyjstormont@gmail.com>
Approved by: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
Ported-by: Tim Chase <tim@chase2k.com>
Signed-off-by: Tim Chase <tim@chase2k.com>
OpenZFS-issue: https://illumos.org/issues/9075
OpenZFS-commit: https://github.com/openzfs/openzfs/commit/619c0123
Closes #7459
2016-07-22 17:39:36 +03:00
|
|
|
extern uint32_t zone_get_hostid(void *zonep);
|
2008-12-11 22:14:49 +03:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Hostname information
|
|
|
|
|
*/
|
2010-05-29 00:45:14 +04:00
|
|
|
extern int ddi_strtoull(const char *str, char **nptr, int base,
|
|
|
|
|
u_longlong_t *result);
|
|
|
|
|
|
2014-10-01 23:02:12 +04:00
|
|
|
typedef struct utsname utsname_t;
|
|
|
|
|
extern utsname_t *utsname(void);
|
|
|
|
|
|
2008-12-11 22:14:49 +03:00
|
|
|
/* ZFS Boot Related stuff. */
|
|
|
|
|
|
|
|
|
|
struct _buf {
|
|
|
|
|
intptr_t _fd;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct bootstat {
|
|
|
|
|
uint64_t st_size;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
extern int zfs_secpolicy_snapshot_perms(const char *name, cred_t *cr);
|
|
|
|
|
extern int zfs_secpolicy_rename_perms(const char *from, const char *to,
|
|
|
|
|
cred_t *cr);
|
|
|
|
|
extern int zfs_secpolicy_destroy_perms(const char *name, cred_t *cr);
|
2016-06-07 19:16:52 +03:00
|
|
|
extern int secpolicy_zfs(const cred_t *cr);
|
2008-12-11 22:14:49 +03:00
|
|
|
extern zoneid_t getzoneid(void);
|
|
|
|
|
|
|
|
|
|
/* SID stuff */
|
|
|
|
|
typedef struct ksiddomain {
|
|
|
|
|
uint_t kd_ref;
|
|
|
|
|
uint_t kd_len;
|
|
|
|
|
char *kd_name;
|
|
|
|
|
} ksiddomain_t;
|
|
|
|
|
|
|
|
|
|
ksiddomain_t *ksid_lookupdomain(const char *);
|
|
|
|
|
void ksiddomain_rele(ksiddomain_t *);
|
|
|
|
|
|
2009-07-03 02:44:48 +04:00
|
|
|
#define DDI_SLEEP KM_SLEEP
|
|
|
|
|
#define ddi_log_sysevent(_a, _b, _c, _d, _e, _f, _g) \
|
|
|
|
|
sysevent_post_event(_c, _d, _b, "libzpool", _e, _f)
|
|
|
|
|
|
Add zstd support to zfs
This PR adds two new compression types, based on ZStandard:
- zstd: A basic ZStandard compression algorithm Available compression.
Levels for zstd are zstd-1 through zstd-19, where the compression
increases with every level, but speed decreases.
- zstd-fast: A faster version of the ZStandard compression algorithm
zstd-fast is basically a "negative" level of zstd. The compression
decreases with every level, but speed increases.
Available compression levels for zstd-fast:
- zstd-fast-1 through zstd-fast-10
- zstd-fast-20 through zstd-fast-100 (in increments of 10)
- zstd-fast-500 and zstd-fast-1000
For more information check the man page.
Implementation details:
Rather than treat each level of zstd as a different algorithm (as was
done historically with gzip), the block pointer `enum zio_compress`
value is simply zstd for all levels, including zstd-fast, since they all
use the same decompression function.
The compress= property (a 64bit unsigned integer) uses the lower 7 bits
to store the compression algorithm (matching the number of bits used in
a block pointer, as the 8th bit was borrowed for embedded block
pointers). The upper bits are used to store the compression level.
It is necessary to be able to determine what compression level was used
when later reading a block back, so the concept used in LZ4, where the
first 32bits of the on-disk value are the size of the compressed data
(since the allocation is rounded up to the nearest ashift), was
extended, and we store the version of ZSTD and the level as well as the
compressed size. This value is returned when decompressing a block, so
that if the block needs to be recompressed (L2ARC, nop-write, etc), that
the same parameters will be used to result in the matching checksum.
All of the internal ZFS code ( `arc_buf_hdr_t`, `objset_t`,
`zio_prop_t`, etc.) uses the separated _compress and _complevel
variables. Only the properties ZAP contains the combined/bit-shifted
value. The combined value is split when the compression_changed_cb()
callback is called, and sets both objset members (os_compress and
os_complevel).
The userspace tools all use the combined/bit-shifted value.
Additional notes:
zdb can now also decode the ZSTD compression header (flag -Z) and
inspect the size, version and compression level saved in that header.
For each record, if it is ZSTD compressed, the parameters of the decoded
compression header get printed.
ZSTD is included with all current tests and new tests are added
as-needed.
Per-dataset feature flags now get activated when the property is set.
If a compression algorithm requires a feature flag, zfs activates the
feature when the property is set, rather than waiting for the first
block to be born. This is currently only used by zstd but can be
extended as needed.
Portions-Sponsored-By: The FreeBSD Foundation
Co-authored-by: Allan Jude <allanjude@freebsd.org>
Co-authored-by: Brian Behlendorf <behlendorf1@llnl.gov>
Co-authored-by: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Co-authored-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl>
Co-authored-by: Michael Niewöhner <foss@mniewoehner.de>
Signed-off-by: Allan Jude <allan@klarasystems.com>
Signed-off-by: Allan Jude <allanjude@freebsd.org>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Signed-off-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl>
Signed-off-by: Michael Niewöhner <foss@mniewoehner.de>
Closes #6247
Closes #9024
Closes #10277
Closes #10278
2020-08-18 20:10:17 +03:00
|
|
|
/*
|
|
|
|
|
* Kernel modules
|
|
|
|
|
*/
|
|
|
|
|
#define __init
|
|
|
|
|
#define __exit
|
|
|
|
|
|
2020-10-14 07:05:49 +03:00
|
|
|
#endif /* _KERNEL || _STANDALONE */
|
2020-06-06 22:54:04 +03:00
|
|
|
|
|
|
|
|
#ifdef __cplusplus
|
|
|
|
|
};
|
|
|
|
|
#endif
|
|
|
|
|
|
2008-12-11 22:14:49 +03:00
|
|
|
#endif /* _SYS_ZFS_CONTEXT_H */
|