> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/zfs/shou-ce-ye/xi-tong-guan-li-ming-ling-system-administration-8/zpool-export.8.md).

# zpool-export(8)

## 名称

`zpool-export` — 导出 ZFS 存储池

## 概述

```sh
zpool export [-f] [-a | 池名…]
```

## 说明

将给定池从系统中导出。所有设备都会被标记为已导出，但仍被其他子系统视为正在使用。只要存在足够数量的设备，这些设备就可以在系统之间移动（包括字节序不同的系统）并导入。

导出池之前，池内的所有数据集都会被卸载。如果池有一个正在使用中的共享热备盘，则该池无法导出。

要让池具备可移植性，必须给 `zpool` 命令提供整块磁盘而非仅仅分区，这样 ZFS 才能用可移植的 EFI 标签为磁盘打标签；否则，字节序不同的平台上的磁盘驱动器将无法识别这些磁盘。

### `-a`

导出系统上所有已导入的池。

### `-f`

强制卸载所有数据集，并允许导出带活动共享热备盘的池。

此命令即使池的共享热备盘正在使用中也会强制导出。这可能导致数据损坏。

## 示例

### 示例 1：导出 ZFS 存储池

以下命令导出池 `tank` 中的设备，以便移动位置或稍后导入：

```sh
# zpool export tank
```

## 参考文献

zpool-import(8)

2022 年 7 月 11 日


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://book.bsdcn.org/zfs/shou-ce-ye/xi-tong-guan-li-ming-ling-system-administration-8/zpool-export.8.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
