All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <phill@thesusis.net>
To: Borden <borden_c@tutanota.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Connection lost during BTRFS move + resize
Date: Mon, 29 Nov 2021 11:20:28 -0500	[thread overview]
Message-ID: <87mtlnaq2p.fsf@vps.thesusis.net> (raw)
In-Reply-To: <MpgNwtq--3-2@tutanota.com>


Borden <borden_c@tutanota.com> writes:

> For my own education/curiosity/intellectual banter: ddrescue,
> badblocks, rsync and other utilities have log files that track
> progress and allow it to resume if it's interrupted. Since resize
> operations work in the linear process you described, how hard would it
> be, theoretically, to implement a "needle position" in a move
> operation to allow a move to pick up where it left off?

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.



  parent reply	other threads:[~2021-11-29 16:26 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 [this message]
2021-11-29 17:20       ` Borden
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=87mtlnaq2p.fsf@vps.thesusis.net \
    --to=phill@thesusis.net \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.