From: Namjae Jeon <linkinjeon@kernel.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Cc: Eric Sandeen <sandeen@sandeen.net>,
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>
Subject: [ANNOUNCE] exfatprogs-1.2.0 version released
Date: Fri, 28 Oct 2022 19:46:05 +0900 [thread overview]
Message-ID: <CAKYAXd8G1kkpiZbjU2nAWMSffsTXXJeDKorcVrvHptMU3p1jhw@mail.gmail.com> (raw)
Hi folk,
We have released exfatprogs 1.2.0 version. In this release, fsck.exfat
is able to fix(repair) corruptions in exFAT(The previous versions only
check consistency). Also, exfat2img has been added to clone exFAT
storage(only metadata) to the image file.
Any feedback is welcome!:)
CHANGES :
* fsck.exfat: Keep traveling files even if there is a corrupted
directory entry set.
* fsck.exfat: Introduce the option "b" to recover a boot sector even
if an exFAT filesystem is not found.
* fsck.exfat: Introduce the option "s" to create files in
"/LOST+FOUND", which have clusters allocated but was not belonged to
any files.
* fsck.exfat: Rename '.' and '..' entry name to the one user want.
NEW FEATURES :
* fsck.exfat: Repair corruptions of an exFAT filesystem. Please refer
to fsck.exfat manpage to see what kind of corruptions can be repaired.
* exfat2img: Dump metadata of an exFAT filesystem. Please refer to
exfat2img manpage to see how to use it.
BUG FIXES:
* fsck.exfat: Fix an infinite loop while traveling files.
* tune.exfat: Fix bitmap entry corruption when adding new volume lablel.
The git tree is at:
https://github.com/exfatprogs/exfatprogs
The tarballs can be found at:
https://github.com/exfatprogs/exfatprogs/releases/download/1.2.0/exfatprogs-1.2.0.tar.gz
reply other threads:[~2022-10-28 10:46 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=CAKYAXd8G1kkpiZbjU2nAWMSffsTXXJeDKorcVrvHptMU3p1jhw@mail.gmail.com \
--to=linkinjeon@kernel.org \
--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).