Project

General

Profile

Actions
Copy link

Bug #13065

closed

log when suspending a zpool

Added by John Levon almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
John Levon
Category:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

While experimenting with ZFS I/O failures, I hit a situation where the root pool would get suspended,
and due to all writes being hung (failmode=wait), the usual processing of the FMA ereport could not
make enough progress. Or perhaps it's not possible to log in to the system at all to investigate.

As it always requires some intervention to correct a suspended pool, it seems worth logging this
with CE_WARN to give an additional clue as to status.

Side note: https://illumos.org/msg/ZFS-8000-HC appears to incorrectly claim read I/Os are also suspended,
but in practice this isn't the case (and it's not just the ARC: read I/Os to the underlying device are issued and
completed). So often you can make some level of progress still until you stumble over a sync write I/O

Actions
Copy link
 #1

Updated by John Levon almost 2 years ago

I did a simple test on this by making all writes fail for a bhyve VM, and checking the message appears when the pool in the guest was suspended

Actions
Copy link
 #2

Updated by Electric Monk almost 2 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

git commit 8548ec78d85644539a23c4262ed2b9512a47865e

commit  8548ec78d85644539a23c4262ed2b9512a47865e
Author: John Levon <john.levon@joyent.com>
Date:   2020-08-21T14:33:06.000Z

    13065 log when suspending a zpool
    Reviewed by: Andy Fiddaman <andy@omniosce.org>
    Reviewed by: Toomas Soome <tsoome@me.com>
    Approved by: Dan McDonald <danmcd@joyent.com>

Actions
Copy link

Also available in: Atom PDF