Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Vytautas D <vytdau@gmail.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas for btrfs-convert fix(or rework)
Date: Thu, 12 Nov 2015 08:27:49 -0500	[thread overview]
Message-ID: <564493D5.2070609@gmail.com> (raw)
In-Reply-To: <CAO5K3OfBy72Yn1s4Ow2h_2KkE7U4wQA66oxjQLva82-D2LqScA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

On 2015-11-12 05:23, Vytautas D wrote:
> [ resending as it didnt get through. ]
>
> I got different opinion. btrfs-convert is something that
> brought me to btrfs. While there are other bugs to fix, someone
> dedicating time to fix btrfs-convert is of high interest to me.
> Sending right message to community, might make some rolling distros to
> trust it and experiment with it.
While I can kind of understand this, what has been said about it being 
something you run exactly once per-system per-filesystem is not untrue 
for almost all users.  It has almost no value for people setting up new 
systems (because they can just use BTRFS directly), and I personally see 
very limited value for the two biggest rolling-release distros that I 
know of (Arch and Gentoo), because the very fact that you installed a 
system with either one means that you are fully capable of backing up 
your data, and reprovisioning the system using BTRFS instead of whatever 
filesystem you are already using (and that will _always_ be safer than 
in-place conversion).  I also see little value for non rolling-release 
systems other than Ubuntu (and possibly Mint, I don't know if they have 
reliably working in-place release upgrades or not) because system 
upgrades with those are usually full re-installs (and by the time that 
btrfs-convert has been around long enough that they consider it safe to 
package, BTRFS will be a lot more prevalent and will likely have been 
the default FS for them for a long time).


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-11-12 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10  6:27 Ideas for btrfs-convert fix(or rework) Qu Wenruo
2015-11-10  7:55 ` Roman Mamedov
2015-11-10  8:16   ` Qu Wenruo
2015-11-10  9:08     ` Roman Mamedov
2015-11-10  9:18       ` Qu Wenruo
2015-11-10 10:31         ` Duncan
2015-11-12 10:23           ` Vytautas D
2015-11-12 13:27             ` Austin S Hemmelgarn [this message]
2015-11-12 14:09               ` Roman Mamedov
2015-11-12 14:38                 ` Austin S Hemmelgarn
2015-11-13  6:41                   ` Duncan
2015-11-16 17:46 ` David Sterba
2015-11-17  0:42   ` Qu Wenruo

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=564493D5.2070609@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=vytdau@gmail.com \
    /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