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>, Ivan Shapovalov <intelfx100@gmail.com>
Cc: "Milan Buška" <milan.buska@gmail.com>,
	"ReiserFS Development List" <reiserfs-devel@vger.kernel.org>,
	debian-boot@lists.debian.org, debian-kernel@lists.debian.org
Subject: Re: Reiser4: Format 4.0.1: Meta(data) checksums
Date: Thu, 17 Sep 2015 16:31:17 +0200	[thread overview]
Message-ID: <55FACEB5.6040803@gmail.com> (raw)
In-Reply-To: <CAM12Q5QySio0eJMYe91YQEB19Z+xwmJ6sjVEKDD9Be8TCf5Bvg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2857 bytes --]

Does the attached patch help?

Edward.

On 09/17/2015 02:10 PM, Jose R R wrote:
> On Sun, Sep 13, 2015 at 6:06 AM, Ivan Shapovalov <intelfx100@gmail.com> wrote:
>> On 2015-09-13 at 05:57 -0700, Jose R R wrote:
>>> Here is some additional info:
>>>
>>> A while back, I installed Debian Jessie AMD64 into a KVM virtual
>>> machine and also included the initial non-systemd boot argument:
>>> preseed/late_command="in-target apt-get install -y sysvinit-core"
>>> < https://wiki.debian.org/systemd#Installing_without_systemd >
>>>
>>> Afterwards a previous reiser4-patched Linux kernel 4.0.x was
>>> installed
>>> into the virtual machine and its root fs was subsequently formatted
>>> to
>>> reiser4.. The virtual machine was working fine:
>>> < https://pbs.twimg.com/media/CKIKgoZUAAIFx12.png:large >
>>>
>>> Yesterday, I installed into the vm a newer 4.1.6 kernel built "the
>>> debian way" except that it was customized with the newer 4.0.1
>>> Reiser4
>>> patch. Upon rebooting the VM, I captured a sequence of 4 snapshots
>>> (by
>>> paging down) that basically recreate the fail that I experienced
>>> priorly in the physical machine:
>>>
>>> < https://metztli.it/blog/index.php/ixiptli/non-systemd-debian-sid-re
>>> iser4 >
>>>
>>> Accordingly, seems the *lack of systemd* is enough for a Debian Sid
>>> instance to create a bad initrd.img. I have no idea if issue only
>>> appears with Reiser4 root fs or if it includes other file systems as
>>> root. Work in progress...
>> It's presence/absence of crc32c module that matters. Reiser4 does not
>> specify that it needs one.
>>
> Applied your 3 patches
> 1/3 < http://marc.info/?l=reiserfs-devel&m=144218573602435&w=2 >
> 2/3 < http://marc.info/?l=reiserfs-devel&m=144218573602436&w=2 >
> 3/3 < http://marc.info/?l=reiserfs-devel&m=144218573702437&w=2 >
>
> into kernel.org Linux Kernel 4.1.7, but Non-systemd Debian still boots
> into an emergency shell
> [...]
> mount: mounting /dev/sdaX on /root failed: no such file or directory
> Target fileystem doesn't have requested /sbin/init
> mount: mounting /dev on /root/dev failed: no such file or directory
> No init found. Try passing init= bootarg.
> [...]
>
> Typing dmesg:
> [...]
> reiser4[exe(801)]: reiser4_init_csum_tfm
> (fs/reiser4/checksum.c:11)[intelfx-81]:WARNING: Could not load crc32c
> driver
>
> In a couple of days I will build the kernel "the Debian way"; I will
> specify -- in relevant module section, at file [kernel source
> tree]debian/installer/package-list:
> [...]
>
> Package: reiser4-modules
> Depends: kernel-image crc-modules # <--- will add that
> Priority: extra
> Description: Reiser4 filesystem support
>   This package contains the Reiser4 filesystem module for the kernel.
> [...]
>
> As well as at /usr/share/kernel-wedge/package-list
>
> We will see what happens.
>
>
>> --
>> Ivan Shapovalov / intelfx /
>>
>
>


[-- Attachment #2: reiser4-select-crc32c.patch --]
[-- Type: text/x-patch, Size: 435 bytes --]

Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
 fs/reiser4/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- a/fs/reiser4/Kconfig
+++ b/fs/reiser4/Kconfig
@@ -5,6 +5,7 @@ config REISER4_FS
 	select LZO_COMPRESS
 	select LZO_DECOMPRESS
 	select CRYPTO
+	select CRYPTO_CRC32C
 	help
 	  Reiser4 is a filesystem that performs all filesystem operations
 	  as atomic transactions, which means that it either performs a

  reply	other threads:[~2015-09-17 14:31 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
     [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 [this message]
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=55FACEB5.6040803@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=debian-boot@lists.debian.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=intelfx100@gmail.com \
    --cc=jose.r.r@metztli.com \
    --cc=milan.buska@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).