linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: linux-erofs@lists.ozlabs.org
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] erofs-utils: release 1.4
Date: Mon, 22 Nov 2021 01:24:56 +0800	[thread overview]
Message-ID: <20211121172455.GA8626@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)

Hi folks,

A new version erofs-utils 1.4 is available at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git tags/v1.4

It mainly includes the following changes:
   - (experimental) introduce preliminary dump.erofs (Wang Qi, Guo Xuenan);
   - (experimental) introduce preliminary fsck.erofs (Daeho Jeong);
   - introduce MicroLZMA compression support (thanks to Lasse Collin);
   - support chunk-based uncompressed files for deduplication;
   - support multiple devices for multi-blob CAS container images;
   - (mkfs.erofs, AOSP) add block list support (Yue Hu, David Anderson);
   - (mkfs.erofs) support per-inode compress pcluster hints (Huang Jianan);
   - (mkfs.erofs) add "noinline_data" extended option for DAX;
   - (mkfs.erofs) introduce --quiet option (suggested by nl6720);
   - complete MacOS build & functionality;
   - various bugfixes and cleanups;

Many noticeable updates here. First, new preliminary fsck.erofs and
dump.erofs are now added to analyse and check EROFS images by Daeho
Jeong, Wang Qi and Guo Xuenan. More improvements about those features
will be shown in the future versions.

Thanks to Lasse Collin, LZMA (specifically MicroLZMA) compression
support is also finalized in this version. (btw, tail-packing inline
for compressed data is now ongoing by Yue Hu [1] which will be
addressed in the next version.)

Also, in order to support chunk deduplication and some container use
cases, chunk-based files and multiple devices are supported in this
version. As usual, add a word here, our team will announce the new
opensource Nydus container image service [2] implemented in the Rust
language at Open Source Summit 2021 China which aims to use a minimal
metadata (EROFS-compatible RAFS v6) + a few content-addressed
chunk-based de-duplicated blobs for effective distribution as well as
storage (such as minimizing underlay fs metadata overhead). It's still
under some internal release processes so please stay tuned..

In addition, users can now write their own per-file pcluster hints
to adjust compression unit size for each file, which was contributed
by Huang Jianan. There are also some AOSP-specific features to make
Android scenarios work better as always.

In the end, we are actively working on more useful scenarios [3] and
quite happy to hear, implement and enhance any useful feature requests
from communities. Feel free to feedback any comments, questions, bugs,
suggestions, etc. to us for better improvements and welcome to join us
as well :-)

Thanks,
Gao Xiang

[1] https://lore.kernel.org/r/b1b3b72371dd4a6b46137dce2fab04899e111df9.1637140430.git.huyue2@yulong.com 
[2] https://github.com/dragonflyoss/image-service
[3] https://lore.kernel.org/r/20211009061150.GA7479@hsiangkao-HP-ZHAN-66-Pro-G1

                 reply	other threads:[~2021-11-21 17:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211121172455.GA8626@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=xiang@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 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).