Project

General

Profile

Bug #5140

message about "%recv could not be opened" is printed when booting after crash

Added by Matthew Ahrens about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Category:
zfs - Zettabyte File System
Start date:
2014-09-07
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

After crashing, the ZIL tries to open all filesystems to claim their log
blocks. If we were in the middle of a receive, then there will be a "%recv"
filesystem, which is marked inconsistent. Because it's inconsistent, it can't
be opened, so the ZIL prints a warning message on the console. The warning
message is not necessary, and shouldn't be printed. The %recv filesystem can't
have any log blocks, so the ZIL doesn't need to open it.

History

#1

Updated by Electric Monk about 5 years ago

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

git commit 22438533bcc131ecebd4c16c699c35e91d321b76

commit  22438533bcc131ecebd4c16c699c35e91d321b76
Author: Matthew Ahrens <mahrens@delphix.com>
Date:   2014-09-11T07:05:49.000Z

    5140 message about "%recv could not be opened" is printed when booting after crash
    Reviewed by: Christopher Siden <christopher.siden@delphix.com>
    Reviewed by: George Wilson <george.wilson@delphix.com>
    Reviewed by: Max Grossman <max.grossman@delphix.com>
    Reviewed by: Richard Elling <richard.elling@gmail.com>
    Approved by: Dan McDonald <danmcd@omniti.com>

Also available in: Atom PDF