From: Edward Shishkin <edward.shishkin@gmail.com>
To: Reiserfs development mailing list <reiserfs-devel@vger.kernel.org>
Subject: Reiser4: Format 4.0.1: Meta(data) checksums
Date: Mon, 31 Aug 2015 17:21:04 +0200 [thread overview]
Message-ID: <55E470E0.2070304@gmail.com> (raw)
Hi all,
This is the first release of new software versions of reiser4 kernel
module and reiser4prods, which invoke the builtin mechanism of
tracking compatibility basing on versions of reiser4 plugin library.
More about this can be found here:
https://reiser4.wiki.kernel.org/index.php/Reiser4_development_model
Reiser4progs of the new software release version number 4.0.1
are provided by the package reiser4progs-1.1.0. Please find here:
https://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs
Reiser4 kernel module of the new software release version number
4.0.1 is provided by the patch reiser4-for-4.1.5. Please find here:
https://sourceforge.net/projects/reiser4/files/reiser4-for-linux-4.x/
At mount time disk format version of your partition's superblock will
be upgraded by the kernel, and you will be suggested to complete the
upgrade offline by fsck:
# dmesg | grep [rR]eiser4
Loading Reiser4 (format release: 4.0.1).
reiser4: sda5: found disk format 4.0.0.
reiser4: sda5: upgrading disk format to 4.0.1.
reiser4: sda5: use 'fsck.reiser4 --fix' to complete disk format upgrade.
You may ignore this suggestion and continue to work as usual.
However, I would suggest to find a time and complete the upgrade.
NOTE: after mount in the new kernel you won' t be able to
check your partition by reiser4progs-1.0.9 and older versions, so
please upgrade your reiser4progs BEFORE. Everyone who relies on
liveCDs with reiser4progs-1.0.9, or older versions: be careful!
More about reiser4 (meta)data checksums can be found here:
https://reiser4.wiki.kernel.org/index.php/Reiser4_checksums
Thanks,
Edward.
next reply other threads:[~2015-08-31 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 15:21 Edward Shishkin [this message]
2015-09-08 20:46 ` Reiser4: Format 4.0.1: Meta(data) checksums Jose R R
2015-09-08 21:21 ` Edward Shishkin
[not found] ` <CAFCWPPL+qqq0UgqV0F2T54EfmvVYmN6iWeuoVNvExR+dYqZWmg@mail.gmail.com>
2015-09-09 7:54 ` Jose R R
2015-09-09 13:16 ` Ivan Shapovalov
2015-09-10 11:57 ` Jose R R
2015-09-10 12:10 ` Ivan Shapovalov
2015-09-13 12:57 ` Jose R R
2015-09-13 13:06 ` Ivan Shapovalov
2015-09-17 12:10 ` Jose R R
2015-09-17 14:31 ` Edward Shishkin
2015-09-17 15:56 ` Ivan Shapovalov
2015-09-17 21:51 ` Ben Hutchings
2015-09-18 9:51 ` Ivan Shapovalov
2015-09-18 11:02 ` Ben Hutchings
2015-09-20 13:48 ` Jose R R
2015-09-20 14:10 ` Ivan Shapovalov
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=55E470E0.2070304@gmail.com \
--to=edward.shishkin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).