linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: sedat.dilek@gmail.com
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@sandeen.net>,
	Goldwyn Rodrigues <rgoldwyn@suse.com>,
	Nicolas Boos <nicolas.boos@wanadoo.fr>,
	Hyunchul Lee <hyc.lee@gmail.com>,
	Luca Stefani <luca.stefani.ge1@gmail.com>,
	Matthieu CASTET <castet.matthieu@free.fr>,
	Sven Hoexter <sven@stormbind.net>,
	Ethan Sommer <e5ten.arch@gmail.com>,
	Hyeongseok Kim <hyeongseok@gmail.com>
Subject: Re: exfatprogs-1.0.4 version released
Date: Sun, 2 Aug 2020 08:36:33 +0900	[thread overview]
Message-ID: <CAKYAXd-VCQrJqP_dfM+wPEf4nPhuqhu3F=9cGeNCOGzFmPZwjw@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUX8KWtdDpMcmzqp461ndcyfvP13gaZK591OFpkp3nRHaQ@mail.gmail.com>

2020-07-31 18:56 GMT+09:00, Sedat Dilek <sedat.dilek@gmail.com>:
> On Fri, Jul 31, 2020 at 9:16 AM Namjae Jeon <namjae.jeon@samsung.com>
> wrote:
>>
>> Hi folk,
>>
>> In this release, The performance of fsck have been much improved and
>> the new option in mkfs have been added to adjust boundary alignment.
>>
>> As the result below, The fsck performance is improved close to windows's
>> fsck
>> and much faster than the one in exfat-utils package.
>>
>> We measured the performance on Samsung 64GB Pro microSDXC UHS-I Class 10
>> which
>> was filled up to 35GB with 9948 directories and 16506 files.
>>
>> | Implementation       | version           | execution time (seconds) |
>> |--------------------- |-------------------|--------------------------|
>> | **exfatprogs fsck**  | 1.0.4             | 11.561                   |
>> | Windows fsck         | Windows 10 1809   | 11.449                   |
>> | [exfat-fuse fsck]    | 1.3.0             | 68.977                   |
>>
>
> Hi Namjae Jeon (what is your First name and Family name?),
Hi Sedat,
First name : Namjae, Last name : Jeon
>
> congrats to version 1.0.4 and hope to see it in the Debian repositories
> soon.
Thanks:)
>
> Great numbers for exfatprogs/fsck!
>
>> And we have been preparing to add fsck repair feature in the next
>> version.
>> Any feedback is welcome!:)
>>
>> CHANGES :
>>  * fsck.exfat: display sector, cluster, and volume sizes in the human
>>    readable format.
>>  * fsck.exfat: reduce the elapsed time using read-ahead.
>>
>> NEW FEATURES :
>>  * mkfs.exfat: generate pseudo unique serials while creating filesystems.
>>  * mkfs.exfat: add the "-b" option to align the start offset of FAT and
>>    data clusters.
>>  * fsck.exfat: repair zero-byte files which have the NoFatChain
>> attribute.
>>
>> BUG FIXES :
>>  * Fix memory leaks on error handling paths.
>>  * fsck.exfat: fix the bug that cannot access space beyond 2TB.
>>
>> The git tree is at:
>>       https://github.com/exfatprogs/exfatprogs
>>
>> The tarballs can be found at:
>>
>> https://github.com/exfatprogs/exfatprogs/releases/download/1.0.4/exfatprogs-1.0.4.tar.gz
>>
>
> Just a small nit for the next announcement.
> Please point (also) to the tar.xz tarball and maybe to the releases
> tag in GitHub.
Sure. I will do that on next release.
> ( Today, I love/prefer to use ZSTD where possible - that is another story.
> )
I'm not sure if it is meaningful to provide various compression for
small archive file. In particular, I wonder if other distribution
maintainers want it.
>
> Have more fun.
Nice day!
>
> Regards,
> - Sedat -
>
> [1]
> https://github.com/exfatprogs/exfatprogs/releases/download/1.0.4/exfatprogs-1.0.4.tar.xz
> [2] https://github.com/exfatprogs/exfatprogs/releases/tag/1.0.4
>

      parent reply	other threads:[~2020-08-01 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200731071604epcas1p39fe86c3931c5adf9073817c12fb15f1d@epcas1p3.samsung.com>
2020-07-31  7:16 ` exfatprogs-1.0.4 version released Namjae Jeon
2020-07-31  9:56   ` Sedat Dilek
2020-07-31 10:53     ` Sedat Dilek
2020-08-01 23:36     ` Namjae Jeon [this message]

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='CAKYAXd-VCQrJqP_dfM+wPEf4nPhuqhu3F=9cGeNCOGzFmPZwjw@mail.gmail.com' \
    --to=linkinjeon@kernel.org \
    --cc=castet.matthieu@free.fr \
    --cc=e5ten.arch@gmail.com \
    --cc=hyc.lee@gmail.com \
    --cc=hyeongseok@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.stefani.ge1@gmail.com \
    --cc=namjae.jeon@samsung.com \
    --cc=nicolas.boos@wanadoo.fr \
    --cc=rgoldwyn@suse.com \
    --cc=sandeen@sandeen.net \
    --cc=sedat.dilek@gmail.com \
    --cc=sven@stormbind.net \
    /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).