From: Edward Shishkin <edward.shishkin@gmail.com>
To: Reiserfs mailing list <reiserfs-devel@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: "Mathieu Bélanger" <b747xx@gmail.com>
Subject: Reiser4progs-1.0.7
Date: Sat, 17 Jan 2009 00:44:25 +0300 [thread overview]
Message-ID: <4970FFB9.2060006@gmail.com> (raw)
Hello everyone.
Changes since reiser4progs-1.0.6:
. Fixed bug in fsck reported by Mathieu Bélanger
(incorrect checking compressed file bodies);
. Alias -p "preen" to -a "auto" for fsck options;
. Suppressed per-object fsck reports about wrong bytes for
files with data checksumming. Use fsck option --fix to
set up their correct values (in the case of transparent
compression i_blocks and i_bytes are not supported
by kernel for performance reasons). If bytes are wrong
because of fatal corruptions, then fsck will report about
last ones.
All the patches were announced at reiserfs-devel mailing list.
Please, find at
http://www.kernel.org/pub/linux/utils/fs/reiser4/reiser4progs/
Thanks,
Edward.
reply other threads:[~2009-01-16 21:42 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=4970FFB9.2060006@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=b747xx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@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