reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Jose R R <jose.r.r@metztli.com>
Cc: Reiserfs development mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4: Format 4.0.1: Meta(data) checksums
Date: Tue, 08 Sep 2015 23:21:25 +0200	[thread overview]
Message-ID: <55EF5155.2040701@gmail.com> (raw)
In-Reply-To: <CAM12Q5Qkx-3ShOJjXd02_4Af0it3wv+39hXDW4sFhBosg=i3SQ@mail.gmail.com>



On 09/08/2015 10:46 PM, Jose R R wrote:
> Niltze, Ed-

Hello

>
>
>
> On Mon, Aug 31, 2015 at 8:21 AM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>> 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.
>> --
>> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> I have applied reiser4-for-4.1.5.patch.gz to both pristine
> linux-4.1.5.tar.xz from kernel.org and to 4.1.6 from upstream Debian
> and both kernels fail to (re)boot into the Reiser4 root partition in
> which they were built.
>
> I am using Debian Sid reiser4progs_1.1.0-1_amd64.deb from
> https://packages.debian.org/sid/reiser4progs
>
> In both instances, after GRUB boots from the boot partition into the
> root Reiser4 partition and message after
> fsck.reiser4 /dev/sdaX
> [ 3.979349 ] BUG: unable to handle kernel NULL pointer dereference at
> 0000000000000069


Could you catch the full stack dump at serial console,
or take a pic of this by using camera?

Thanks,
Edward.


> [...]
> (initramfs prompt) will not boot into its Reiser4 partition
>
>  From another partition I have even tried (using
> reiser4progs_1.1.0-1_amd64.deb, too)
> fsck.reiser4 --version
> fsck.reiser4 1.1.0
> Format release: 4.0.1
> Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
> reiser4progs/COPYING.
>
> fsck.reiser4 --fix /dev/sdaX
> and
> fsck.reiser4  --build-fs /dev/sdaX
>
> which finished fine. Nevertheless upon rebooting into fsck'ed
> partition with the Reiser4 4.0.1 kernel module nothing changes, i.e.,
> I get BUG and kernel boot stops at initramfs prompt.
>
>
> Best Professional Regards.
>


  reply	other threads:[~2015-09-08 21:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 15:21 Reiser4: Format 4.0.1: Meta(data) checksums Edward Shishkin
2015-09-08 20:46 ` Jose R R
2015-09-08 21:21   ` Edward Shishkin [this message]
     [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=55EF5155.2040701@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=jose.r.r@metztli.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).