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: Fri, 2 Aug 2024 20:21:08 +0300	[thread overview]
Message-ID: <789D4B76-7A94-427B-91F1-AF8852181392@me.com> (raw)
In-Reply-To: <4WbC486kcJzlgVnN@009.lax.mailroute.net>



> On 2. Aug 2024, at 20:09, John D Groenveld via illumos-discuss <discuss@lists.illumos.org> wrote:
> 
> In message <1c2abfa3-df73-91cb-79da-c34eaeca3af7@kit.edu>, "Udo Grabowski (IMK)" writes:
>> Did some more testing, could also import it on an 8 years old pool
>> (illumos-a90d75b) with all the features (known at that time) active or enab=
>> led:
> 
> I'm not able to reproduce.
> Here's my test procedure:
> Booted 151a8
> Created two pools:
> # mkfile 64M /root/features
> # mkfile 64M /root/version28
> # zpool create features /root/features
> # zpool create -d -o version=28 version28 /root/version28
> # zfs create features/test
> # zfs create version28/test
> # dd if=/dev/urandom of=/features/test/wee bs=1024k count=16
> # md5sum /features/test/wee
> # cp /features/test/wee /version28/test/
> # md5sum /version28/test/wee
> # zfs snapshot features/test@foo
> # zfs snapshot version28/test@bar
> # zfs send features/test@foo>features.snapshot
> # zfs send version28/test@bar>version28.snapshot
> 
> copy the snapshots to today's OI, illumos-533d257436
> 
> # zfs receive -v rpool/features< features.snapshot
> # zfs receive -v rpool/version28< version28.snapshot
> # md5sum rpool/features/test/wee
> # md5sum rpool/version28/test/wee
> 
> John
> groenveld@acm.org

I’m afraid it is related to specific feature; we would need to get list of enabled and active features from receiving side (as sending side does not have features).

And then there is a question what is specific about that file which is triggering the receive error…  is it possible to get hands on send stream maybe?

(I’m investigating one send+receive case which is triggering receiving pool to get to suspended state and it is quite a challenge).

rgds,
toomas

> 
> ------------------------------------------
> illumos: illumos-discuss
> Permalink: https://illumos.topicbox.com/groups/discuss/T575f82eecd117456-M395c4264e64bbddd3f0ef346
> Delivery options: https://illumos.topicbox.com/groups/discuss/subscription


  reply	other threads:[~2024-08-02 17:21 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 ` [discuss] " Toomas Soome
2024-08-01 12:26   ` 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 [this message]
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=789D4B76-7A94-427B-91F1-AF8852181392@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).