> 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-clear.8.md).

# zpool-clear(8)

## 名称

`zpool-clear` — 清除 ZFS 存储池中的设备错误

## 概述

```sh
zpool clear [--power] 池名 [设备…]
```

## 说明

清除池中的设备错误。未指定参数时，清除池内的所有设备错误；指定一个或多个设备时，只清除与这些设备关联的错误。

如果池曾被挂起，只要设备可以访问，就会把它恢复上线。启用了 `multihost` 的池在被挂起后，若有证据表明该池曾被另一台主机导入，则无法恢复。清除操作开始前，会执行与导入时相同的检查。

### `--power`

为存储机箱中该设备的插槽通电，并等待设备出现后再尝试清除错误。这会对所有指定的设备执行。也可以设置 `ZPOOL_AUTO_POWER_ON_SLOT` 环境变量以始终启用此行为。注意：该选项目前仅在 Linux 上有效。

## 参考文献

zdb(8)、zpool-reopen(8)、zpool-status(8)

2024 年 4 月 29 日


---

# 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-clear.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.
