From: Zdenek Kabelac <zkabelac@redhat.com>
To: "heming.zhao@suse.com" <heming.zhao@suse.com>,
LVM general discussion and development <linux-lvm@redhat.com>,
David Teigland <teigland@redhat.com>
Subject: Re: [linux-lvm] Does LVM have any plan/schedule to support btrfs in fsadm
Date: Fri, 25 Jun 2021 12:57:23 +0200 [thread overview]
Message-ID: <2d5ff29e-2836-0407-ce76-271255487baa@redhat.com> (raw)
In-Reply-To: <ba88aa20-e176-0a07-5578-20afb39e0950@suse.com>
Dne 25. 06. 21 v 7:28 heming.zhao@suse.com napsal(a):
> Hello Zdenek & David,
>
> From URL: https://fedoraproject.org/wiki/Btrfs
> The btrfs becomes default filesystem for desktops.
>
> Do we have any plan to add btrfs code for scripts/fsadm.sh?
>
> If the answer is yes. I could share a suse special patch, this patch
> had been run about 4 years in suse products.
Hi
If you have some patches provided with some good usable testing (lvm2 test
suite) - it could be possibly merged.
On the other hand helping/suggesting users to use Btrfs on top of lvm2 has
also its logical 'question' marks. Since btrfs users should probably be
avoiding placing 'another' layer between real hw - when btrfs should be mostly
capable handling lvm2 features in its 'very own' way. Each layer has it's own
measurable costs. And yeah we do not want to be involved into btrfs related
recovery cases, as we simply never understood its handling of attached disks.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2021-06-25 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 5:28 [linux-lvm] Does LVM have any plan/schedule to support btrfs in fsadm heming.zhao
2021-06-25 10:57 ` Zdenek Kabelac [this message]
2021-06-27 17:40 ` heming.zhao
2021-06-28 3:28 ` Stuart D Gathman
2021-06-28 7:29 ` Gionatan Danti
2021-06-28 23:00 ` Chris Murphy
2021-06-29 22:32 ` Gionatan Danti
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=2d5ff29e-2836-0407-ce76-271255487baa@redhat.com \
--to=zkabelac@redhat.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@redhat.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;
as well as URLs for NNTP newsgroup(s).