On Thu, Oct 28, 2021 at 03:36:10PM +0800, Qu Wenruo wrote:
> Gentle ping?
>
> Without this patch, the new mkfs.btrfs NO_HOLES feature would break any
> kernel/initramfs with hole in it.
Just to clarify, it's not a new feature, it's been out for a long time
(since 3.14). The new thing is that it
On Tue, Nov 05, 2019 at 01:18:41PM +0100, Daniel Kiper wrote:
> On Mon, Nov 04, 2019 at 05:23:22PM +0100, David Sterba wrote:
> > There are new 3- and 4-copy variants of RAID1, estimated to be merged to
> > kernel 5.5. Add the two new profiles to the list of recognized ones. As
>
On Tue, Nov 05, 2019 at 09:19:59AM +, Michael Chang wrote:
> The zstd support in btrfs has dependenciy to zstd module and core.img
> grows its size significantly to 75KB on my system. The resulted image
> cannot be installed into btrfs bootloader area in the size of 64KB and
> eventually fails
There are new 3- and 4-copy variants of RAID1, estimated to be merged to
kernel 5.5. Add the two new profiles to the list of recognized ones. As
this builds on the same code as RAID1, only the redundancy level needs
to be adjusted, the rest is done by the existing code.
Signed-off-by: David
x27;, UUID
f6d3e26c-4d6c-407d-b981-7aa6d842578a - Sector size 512B - Total size 5939200KiB
Device host: Filesystem type hostfs - Sector size 512B - Total size 0KiB
umount: /tmp/tmp.1I3JDrkI64/btrfs_zstd_rw: not mounted.
--
There must be something I'm missing, please advise. Thanks.
David
On Wed, Oct 31, 2018 at 07:48:08PM +0100, Goffredo Baroncelli wrote:
> On 31/10/2018 13.06, Daniel Kiper wrote:
> [...]
> >
> > v11 pushed.
> >
> > Goffredo, thank you for doing the work.
>
> Great ! Many thanks for your support !!
Thank you very much for the work! I've updated wiki with the go
upstream kernel zstd library
> for ease of review.
>
> Thanks to David Sterba for starting this project! I started my patch from
> where he left off.
The first patch did not make it to vger.kernel.org mailinglist, which
suggests that it's big, and possibly too big for merging. I
