Skip to content

Commit

Permalink
Import msg A5/14/JQ (#43)
Browse files Browse the repository at this point in the history
Signed-off-by: bunder2015 <[email protected]>
Issue #41
  • Loading branch information
bunder2015 authored Dec 23, 2018
1 parent 118a999 commit e3bfc6d
Show file tree
Hide file tree
Showing 3 changed files with 275 additions and 0 deletions.
90 changes: 90 additions & 0 deletions msg/ZFS-8000-14/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
<html>
<head>
<title>ZFS Message ID: ZFS-8000-14</title>
</head>
<body>
<!--
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
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
-->
<!-- start: templates/success -->
<!-- ident "@(#)success 1.4 02/14/14 SMI" -->
Article for Message ID:&nbsp;&nbsp; <font size="+1"><tt><b>ZFS-8000-14</b></tt></font>
<br><br>
<hr>
<br><br>
<!-- end: templates/success -->
<!-- start: article -->
<!-- code: ZFS-8000-14 -->
<!-- keys: ereport.fs.zfs.pool.corrupt_cache -->
<table width="80%"><tr><td>
<b>Corrupt ZFS cache</b>
<p>
<dl>
<dt><p><b>Type</b>
<dd>Error
<dt><p><b>Severity</b>
<dd>Critical
<dt><p><b>Description</b>
<dd>The ZFS cache file is corrupted
<dt><p><b>Automated Response</b>
<dd>No automated response will be taken.
<dt><p><b>Impact</b>
<dd>ZFS filesystems are not available.
<dt><p><b>Suggested Action for System Administrator</b>
<dd>
<p>ZFS keeps a list of active pools on the filesystem to avoid having to
scan all devices when the system is booted. If this file is corrupted, then
normally active pools will not be automatically opened. The pools can be
recovered using the 'zpool import' command:</p>

<pre># zpool import
pool: test
id: 12743384782310107047
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:

test ONLINE
sda9 ONLINE
</pre>

<p>This will automatically scan <tt>/dev</tt> for any
devices part of a pool. If devices have been made available in an alternate
location, use the '-d' option to 'zpool import' to search for devices in a
different directory.</p>

<p>Once you have determined which pools are available for import, you can
import the pool explicitly by specifying the name or numeric
identifier:</p>

<pre># zpool import test
</pre>

<p>Alternately, you can import all available pools by specifying the
'-a' option. Once a pool has been imported, the ZFS cache will be repaired so
that the pool will appear normally in the future.</p>
<dt><p><b>Details</b>
<dd>The Message ID: <tt>ZFS-8000-14</tt> indicates a
corrupted ZFS cache file. Take the documented action to resolve the problem.
</dl>
</td></tr></table>
<!-- end: article -->
</body></html>

93 changes: 93 additions & 0 deletions msg/ZFS-8000-A5/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,93 @@
<html>
<head>
<title>ZFS Message ID: ZFS-8000-A5</title>
</head>
<body>
<!--
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
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
-->
<!-- start: templates/success -->
<!-- ident "@(#)success 1.4 02/14/14 SMI" -->
Article for Message ID:&nbsp;&nbsp; <font size="+1"><tt><b>ZFS-8000-A5</b></tt></font>
<br><br>
<hr>
<br><br>
<!-- end: templates/success -->
<!-- start: article -->
<!-- code: ZFS-8000-A5 -->
<!-- keys: ereport.fs.zfs.device.version_mismatch -->
<table width="80%"><tr><td>
<b>Incompatible version</b>
<p>
<dl>
<dt><p><b>Type</b>
<dd>Error
<dt><p><b>Severity</b>
<dd>Major
<dt><p><b>Description</b>
<dd>The on-disk version is not compatible with the running system.
<dt><p><b>Automated Response</b>
<dd>No automated response will occur.
<dt><p><b>Impact</b>
<dd>The pool is unavailable.
<dt><p><b>Suggested Action for System Administrator</b>
<dd>
<p>If this error is seen during 'zpool import', see the section below.
Otherwise, run 'zpool status -x' to determine which pool is faulted:</p>

<pre>
# zpool status -x
pool: test
state: FAULTED
status: The ZFS version for the pool is incompatible with the software running
on this system.
action: Destroy and re-create the pool.
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
<font color='red'> test FAULTED 0 0 0 incompatible version</font>
mirror ONLINE 0 0 0
sda9 ONLINE 0 0 0
sdb9 ONLINE 0 0 0

errors: No known errors
</pre>

<p>The pool cannot be used on this system. Either move the storage to the
system where the pool was originally created, upgrade the current system
software to a more recent version, or destroy the pool and re-create it from
backup.</p>

<p>If this error is seen during import, the pool cannot be imported on the
current system. The disks must be attached to the system which originally
created the pool, and imported there.</p>

<p>The list of currently supported versions can be displayed using 'zpool
upgrade -v'.</p>

<dt><p><b>Details</b>
<dd>The Message ID: <tt>ZFS-8000-A5</tt> indicates a
version mismatch exists between the running system and the on-disk data.
</dl>
</td></tr></table>
<!-- end: article -->
</body></html>

92 changes: 92 additions & 0 deletions msg/ZFS-8000-JQ/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,92 @@
<html>
<head>
<title>ZFS Message ID: ZFS-8000-JQ</title>
</head>
<body>
<!--
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
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
-->
<!-- start: templates/success -->
<!-- ident "@(#)success 1.4 02/14/14 SMI" -->
Article for Message ID:&nbsp;&nbsp; <font size="+1"><tt><b>ZFS-8000-JQ</b></tt></font>
<br><br>
<hr>
<br><br>
<!-- end: templates/success -->
<!-- start: article -->
<!-- code: ZFS-8000-JQ -->
<!-- keys: fault.fs.zfs.io_failure_continue -->
<table width="80%"><tr><td>
<b>ZFS pool I/O failures</b>
<p>
<dl>
<dt><p><b>Type</b>
<dd>Error
<dt><p><b>Severity</b>
<dd>Major
<dt><p><b>Description</b>
<dd>The ZFS pool has experienced currently unrecoverable I/O failures.
<dt><p><b>Automated Response</b>
<dd>No automated response will be taken.
<dt><p><b>Impact</b>
<dd>Write I/Os cannot be serviced.
<dt><p><b>Suggested Action for System Administrator</b>
<dd>
<p>The pool has experienced I/O failures. Since the ZFS pool property 'failmode'
is set to 'continue', read I/Os will continue to be serviced, but write I/Os
are blocked. See the zpool(8) manpage for more information on the 'failmode'
property. Manual intervention is required for write I/Os to be serviced.
You can see which devices are affected by running 'zpool status -x':</p>

<pre># zpool status -x
pool: test
state: FAULTED
status: There are I/O failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
see: https://zfsonlinux.org/msg/ZFS-8000-HC
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
test FAULTED 0 13 0 insufficient replicas
sda9 FAULTED 0 7 0 experienced I/O failures
sdb9 ONLINE 0 0 0

errors: 1 data errors, use '-v' for a list
</pre>

<p>After you have made sure the affected devices are connected, run 'zpool clear'
to allow write I/O to the pool again:
</p>

<pre># zpool clear test
</pre>

<p>If I/O failures continue to happen, then applications and commands for the
pool may hang. At this point, a reboot may be necessary to allow I/O to the
pool again.
</p>
<dt><p><b>Details</b>
<dd>The Message ID: <tt>ZFS-8000-JQ</tt> indicates
that the pool has experienced I/O failures. Take the documented action to resolve the problem.
</dl>
</td></tr></table>
<!-- end: article -->
</body></html>

0 comments on commit e3bfc6d

Please sign in to comment.