From: Namjae Jeon <linkinjeon@kernel.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Goldwyn Rodrigues <rgoldwyn@suse.com>,
Nicolas Boos <nicolas.boos@wanadoo.fr>,
sedat.dilek@gmail.com, 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>,
"Yuezhang.Mo" <Yuezhang.Mo@sony.com>,
Eric Sandeen <sandeen@sandeen.net>,
3394797836@qq.com
Subject: [ANNOUNCE] exfatprogs-1.3.0 version released
Date: Wed, 15 Oct 2025 14:23:38 +0900 [thread overview]
Message-ID: <CAKYAXd8OsoXbJTybYwFTvUe+utUyi9Lw3SMdObgCA82S-b-mQA@mail.gmail.com> (raw)
Hi folks,
In this release, a new tool, defrag.exfat, has been added to perform
defragmentation on exFAT volumes, featuring the following command-line options:
- defrag.exfat /dev/sdX: Perform defragmentation with "fsck warning"
- defrag.exfat -f /dev/sdX: Force defragmentation (skip fsck warning)
- defrag.exfat -a /dev/sdX: Assess current fragmentation status
Additionally, the quick format time of mkfs has been significantly improved:
in the worst-case scenario of a 2TB partition with a 512B cluster size,
the time was reduced from 3 minutes to just 9 seconds.
Any feedback is welcome!:)
NEW FEATURES :
* defrag.exfat: add a tool to defragment an exFAT
filesystem or assess its fragmentation status.
See a man page.
CHANGES :
* mkfs.exfat: minimize zero-out initialization work
in quick format mode to reduce I/O time.
* fsck.exfat: set the entry after an unused entry as unused.
BUG FIXES :
* mkfs.exfat: fix incorrect FAT byte length calculation.
* mkfs.exfat: avoid setting physical sector size into sector_size field.
* fsck.exfat: fix a memory leaks in an error path.
The git tree is at:
https://github.com/exfatprogs/exfatprogs
The tarballs can be found at:
https://github.com/exfatprogs/exfatprogs/releases/download/1.3.0/exfatprogs-1.3.0.tar.gz
reply other threads:[~2025-10-15 5:23 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=CAKYAXd8OsoXbJTybYwFTvUe+utUyi9Lw3SMdObgCA82S-b-mQA@mail.gmail.com \
--to=linkinjeon@kernel.org \
--cc=3394797836@qq.com \
--cc=Yuezhang.Mo@sony.com \
--cc=castet.matthieu@free.fr \
--cc=e5ten.arch@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.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).