public inbox for discuss@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Toomas Soome <tsoome@me.com>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Re: [discuss] Cannot receive older ZFS dumps
Date: Thu, 1 Aug 2024 13:53:14 +0300	[thread overview]
Message-ID: <DC9F9709-4626-49F6-A8C0-3217F2BE0A7A@me.com> (raw)
In-Reply-To: <4d887d0d-140b-949a-a553-71960c26dde8@kit.edu>



> On 1. Aug 2024, at 13:38, Udo Grabowski (IMK) <udo.grabowski@kit.edu> wrote:
> 
> Hi,
> 
> it seems that older zfs images (from zfs send) cannot be imported
> into recent illumos versions. These are dumps from a "pre-features"
> zpool. I get
> 
> ro suntc ~ # cat 32@20100825 | zfs receive -d rpool
> cannot receive new filesystem stream: invalid backup stream


Since we virtually do not develop zfs, it is rather hard to say, but it does sound like bug. However, if you can receive it to pre-feature pool, I would upgrade pre-features pool and then check the send+receive again (from upgraded pool).

rgds,
toomas


> 
> while I can still import those on an older illumos (in oi151.a8).
> 
> This is what zstreamdump sees:
> 
> # cat 32@20100825|zstreamdump
> BEGIN record
>        hdrtype = 1
>        features = 0
>        magic = 2f5bacbac
>        creation_time = 4c751a60
>        type = 2
>        flags = 0x0
>        toguid = d5549c3062863864
>        fromguid = 0
>        toname = Processor/Results/imk/32@20100825
> END checksum = ac3419bb76a98f7/9a5ac336e407bdf3/c07a3f469bc7e40e/f03a369ef26634ee
> SUMMARY:
>        Total DRR_BEGIN records = 1
>        Total DRR_END records = 1
>        Total DRR_OBJECT records = 131771
>        Total DRR_FREEOBJECTS records = 716
>        Total DRR_WRITE records = 133062
>        Total DRR_WRITE_BYREF records = 0
>        Total DRR_WRITE_EMBEDDED records = 0
>        Total DRR_FREE records = 300918
>        Total DRR_SPILL records = 0
>        Total records = 566469
>        Total write size = 1690867200 (0x64c89600)
>        Total stream length = 1902392632 (0x71643538)
> 
> Is this a bug or are "non-feature" dumps in general not importable
> on "feature"-zpools ?
> -- 
> Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
> https://www.imk-asf.kit.edu/english/sat.php
> KIT - Karlsruhe Institute of Technology          https://www.kit.edu
> Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026
> 
> 
> ------------------------------------------
> illumos: illumos-discuss
> Permalink: https://illumos.topicbox.com/groups/discuss/T575f82eecd117456-Mc6ac5b0fc6787f44ca997f22
> Delivery options: https://illumos.topicbox.com/groups/discuss/subscription


  reply	other threads:[~2024-08-01 10:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 10:38 Udo Grabowski (IMK)
2024-08-01 10:53 ` Toomas Soome [this message]
2024-08-01 12:26   ` [discuss] " Udo Grabowski (IMK)
2024-08-02  4:55     ` Joshua M. Clulow
2024-08-02 17:09     ` John D Groenveld
2024-08-02 17:21       ` Toomas Soome
2024-08-02 19:28         ` Richard Lowe
2024-08-05  8:03         ` Udo Grabowski (IMK)
2024-08-05  8:57           ` Toomas Soome
2024-08-05 12:03             ` Udo Grabowski (IMK)
2024-08-05 21:33               ` Joshua M. Clulow
2024-08-05  7:42       ` Udo Grabowski (IMK)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DC9F9709-4626-49F6-A8C0-3217F2BE0A7A@me.com \
    --to=tsoome@me.com \
    --cc=discuss@lists.illumos.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).