public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Borden <borden_c@tutanota.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Connection lost during BTRFS move + resize
Date: Mon, 29 Nov 2021 18:20:36 +0100 (CET)	[thread overview]
Message-ID: <Mpghb5T--3-2@tutanota.com> (raw)
In-Reply-To: <87mtlnaq2p.fsf@vps.thesusis.net>

29 Nov 2021, 11:20 by phill@thesusis.net:
> Theoretically it shouldn't be too hard.  It's just a matter of deciding
> on a location where you can safely record the checkpoint information and
> then update the checkpoint between blocks.  That's how LVM handles
> moves safely.  In the worst case, you restart the move at the last
> checkpoint and just waste some time copying data that was already copied
> but not checkpointed.
>
Thanks again. In those other utilities, since the logs get written to a plain text file of the user's choosing, and partition moving should be offline, anyhow, it would be reasonable to expect the user to provide a safe location to stash a checkpoint file.

And, of course, if the user chooses to manipulate the file and/or forego it altogether, their funeral.
Not sure if it's a feature worth requesting, but it would keep people like me from bothering the list with these Hail Mary support requests, so probably be net-cost negative.

  reply	other threads:[~2021-11-29 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29  8:48 Connection lost during BTRFS move + resize Borden
2021-11-29 15:26 ` Phillip Susi
2021-11-29 15:50   ` Borden
2021-11-29 16:12     ` Graham Cobb
2021-12-01 18:42       ` Matthew Warren
2021-11-29 16:20     ` Phillip Susi
2021-11-29 17:20       ` Borden [this message]
2021-12-03 18:47     ` Chris Murphy
2021-12-03 18:31   ` Chris Murphy

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=Mpghb5T--3-2@tutanota.com \
    --to=borden_c@tutanota.com \
    --cc=linux-btrfs@vger.kernel.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