{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "item": { "id": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "slug": "distinguish-openzfs-import-discovery-from-transaction-discarding-recovery", "url": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery.md", "json": "https://update.dsesecurity.com/api/v1/posts/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/" }, "title": "Distinguish OpenZFS import discovery from transaction-discarding recovery", "summary": "Separate pool discovery from any import option that accepts transaction loss.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-15T13:32:52+00:00", "modified_at": "2026-10-15T13:36:15+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 245, "potentially_affected": "This applies to OpenZFS 2.3 pool import administration. It distinguishes discovery and recovery modes; it is not a recommendation to force an active pool onto another host.", "dse_recommendation": "DSE recommends preserving the initial discovery output and selecting the pool by verified identity before any recovery proposal.", "primary_source": { "name": "OpenZFS 2.3 — zpool import", "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-import.8.html", "published_on": null, "authority": "openzfs.github.io" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Separate pool discovery from any import option that accepts transaction loss.

\n

Source facts

\n

OpenZFS 2.3 import can list available pools and their numeric identifiers before importing one. A numeric identifier distinguishes pools that share a name. Its recovery option, uppercase F, is a different action: it attempts to make a non-importable pool usable by discarding recent transactions, whose data is then irretrievably lost. Combining that recovery option with the documented no-operation check evaluates recoverability without performing the recovery. Uppercase N instead imports without mounting filesystems.

\n

Source: OpenZFS 2.3 — zpool import.

\n

Applicability

\n

This applies to OpenZFS 2.3 pool import administration. It distinguishes discovery and recovery modes; it is not a recommendation to force an active pool onto another host.

\n

DSE recommendation

\n

DSE recommends preserving the initial discovery output and selecting the pool by verified identity before any recovery proposal. Record whether the intended step is listing, importing without mounts, or accepting a specific data-loss boundary. Have a storage specialist review recovery flags and available copies before modifying an unimportable pool. Keep ordinary troubleshooting instructions free of unexplained force or extreme-recovery options. The operator should be able to describe what the chosen command can change before executing it.

\n

Verification

\n

Use disposable exported pools, including duplicate names, to verify identification and no-mount handling. Rehearse any transaction-discarding recovery only on an expendable copy with a documented expected loss boundary. Retain command options and resulting status so discovery evidence cannot be confused with a completed repair.

\n

Official reference

\n

OpenZFS 2.3 — zpool import. Reviewed October 15, 2026.

", "content_text": "Separate pool discovery from any import option that accepts transaction loss.\nSource facts\nOpenZFS 2.3 import can list available pools and their numeric identifiers before importing one. A numeric identifier distinguishes pools that share a name. Its recovery option, uppercase F, is a different action: it attempts to make a non-importable pool usable by discarding recent transactions, whose data is then irretrievably lost. Combining that recovery option with the documented no-operation check evaluates recoverability without performing the recovery. Uppercase N instead imports without mounting filesystems.\nSource: OpenZFS 2.3 — zpool import.\nApplicability\nThis applies to OpenZFS 2.3 pool import administration. It distinguishes discovery and recovery modes; it is not a recommendation to force an active pool onto another host.\nDSE recommendation\nDSE recommends preserving the initial discovery output and selecting the pool by verified identity before any recovery proposal. Record whether the intended step is listing, importing without mounts, or accepting a specific data-loss boundary. Have a storage specialist review recovery flags and available copies before modifying an unimportable pool. Keep ordinary troubleshooting instructions free of unexplained force or extreme-recovery options. The operator should be able to describe what the chosen command can change before executing it.\nVerification\nUse disposable exported pools, including duplicate names, to verify identification and no-mount handling. Rehearse any transaction-discarding recovery only on an expendable copy with a documented expected loss boundary. Retain command options and resulting status so discovery evidence cannot be confused with a completed repair.\nOfficial reference\nOpenZFS 2.3 — zpool import. Reviewed October 15, 2026.", "content_markdown": "Separate pool discovery from any import option that accepts transaction loss.\n\n## Source facts\n\nOpenZFS 2.3 import can list available pools and their numeric identifiers before importing one. A numeric identifier distinguishes pools that share a name. Its recovery option, uppercase F, is a different action: it attempts to make a non-importable pool usable by discarding recent transactions, whose data is then irretrievably lost. Combining that recovery option with the documented no-operation check evaluates recoverability without performing the recovery. Uppercase N instead imports without mounting filesystems.\n\nSource: [OpenZFS 2.3 — zpool import](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-import.8.html).\n\n## Applicability\n\nThis applies to OpenZFS 2.3 pool import administration. It distinguishes discovery and recovery modes; it is not a recommendation to force an active pool onto another host.\n\n## DSE recommendation\n\nDSE recommends preserving the initial discovery output and selecting the pool by verified identity before any recovery proposal. Record whether the intended step is listing, importing without mounts, or accepting a specific data-loss boundary. Have a storage specialist review recovery flags and available copies before modifying an unimportable pool. Keep ordinary troubleshooting instructions free of unexplained force or extreme-recovery options. The operator should be able to describe what the chosen command can change before executing it.\n\n## Verification\n\nUse disposable exported pools, including duplicate names, to verify identification and no-mount handling. Rehearse any transaction-discarding recovery only on an expendable copy with a documented expected loss boundary. Retain command options and resulting status so discovery evidence cannot be confused with a completed repair.\n\n## Official reference\n\n[OpenZFS 2.3 — zpool import](https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-import.8.html). Reviewed October 15, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "url": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Distinguish OpenZFS import discovery from transaction-discarding recovery", "item": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/#article", "identifier": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "url": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/", "headline": "Distinguish OpenZFS import discovery from transaction-discarding recovery", "description": "Separate pool discovery from any import option that accepts transaction loss.", "abstract": "Separate pool discovery from any import option that accepts transaction loss.", "articleBody": "Separate pool discovery from any import option that accepts transaction loss.\nSource facts\nOpenZFS 2.3 import can list available pools and their numeric identifiers before importing one. A numeric identifier distinguishes pools that share a name. Its recovery option, uppercase F, is a different action: it attempts to make a non-importable pool usable by discarding recent transactions, whose data is then irretrievably lost. Combining that recovery option with the documented no-operation check evaluates recoverability without performing the recovery. Uppercase N instead imports without mounting filesystems.\nSource: OpenZFS 2.3 — zpool import.\nApplicability\nThis applies to OpenZFS 2.3 pool import administration. It distinguishes discovery and recovery modes; it is not a recommendation to force an active pool onto another host.\nDSE recommendation\nDSE recommends preserving the initial discovery output and selecting the pool by verified identity before any recovery proposal. Record whether the intended step is listing, importing without mounts, or accepting a specific data-loss boundary. Have a storage specialist review recovery flags and available copies before modifying an unimportable pool. Keep ordinary troubleshooting instructions free of unexplained force or extreme-recovery options. The operator should be able to describe what the chosen command can change before executing it.\nVerification\nUse disposable exported pools, including duplicate names, to verify identification and no-mount handling. Rehearse any transaction-discarding recovery only on an expendable copy with a documented expected loss boundary. Retain command options and resulting status so discovery evidence cannot be confused with a completed repair.\nOfficial reference\nOpenZFS 2.3 — zpool import. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:32:52+00:00", "dateModified": "2026-10-15T13:36:15+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/distinguish-openzfs-import-discovery-from-transaction-discarding-recovery/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Distinguish OpenZFS import discovery from transaction-discarding recovery" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 245, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "OpenZFS 2.3 — zpool import", "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-import.8.html" } } ] } }