All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is btrfs-convert able to deal with sparse files in a ext4 filesystem?
Date: Sun, 2 Apr 2017 09:30:46 +0300	[thread overview]
Message-ID: <c5472e71-908c-3d42-ee40-73d003bfc598@gmail.com> (raw)
In-Reply-To: <pan$df213$fa344dca$8529fcec$34b89ea9@cox.net>

02.04.2017 03:59, Duncan пишет:
> 
> 4) In fact, since an in-place convert is almost certainly going to take 
> more time than a blow-away and restore from backup,

This caught my eyes. Why? In-place convert just needs to recreate
metadata. If you have multi-terabyte worth of data copying them twice
hardly can be faster.

  reply	other threads:[~2017-04-02  6:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01  9:48 Is btrfs-convert able to deal with sparse files in a ext4 filesystem? Kai Herlemann
2017-04-01 19:13 ` Sean Greenslade
2017-04-02  0:59   ` Duncan
2017-04-02  6:30     ` Andrei Borzenkov [this message]
2017-04-03  8:41       ` Roman Mamedov
2017-04-07  3:26       ` Duncan
2017-04-03  1:04 ` Qu Wenruo
2017-04-03 12:32 ` Austin S. Hemmelgarn
2017-04-07 18:24 ` Kai Herlemann

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=c5472e71-908c-3d42-ee40-73d003bfc598@gmail.com \
    --to=arvidjaar@gmail.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.