reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Shapovalov <intelfx100@gmail.com>
To: Jose R R <jose.r.r@metztli.com>
Cc: "Edward Shishkin" <edward.shishkin@gmail.com>,
	"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 18:56:31 +0300	[thread overview]
Message-ID: <1442505391.4102.6.camel@gmail.com> (raw)
In-Reply-To: <CAM12Q5QySio0eJMYe91YQEB19Z+xwmJ6sjVEKDD9Be8TCf5Bvg@mail.gmail.com>

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

On 2015-09-17 at 05:10 -0700, 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-si
> > > d-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.
> [...]

Correct; it's now a "cleanly" reported error instead of an oops.
You will have to manually add crc32c or crc32c_intel module to the
initramfs, though. I could not find a way to express an explicit
intermodule dependency in the code (to make module reiser4 depend on
module crc32c).

Edward's patch selects module crc32c when reiser4 is selected in the
build config, but it does not make sure that crc32c will end up in the
initramfs if reiser4 is there (that is, modules.dep will not be
altered). I'm still wondering how to do that properly.

-- 
Ivan Shapovalov / intelfx /


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  parent reply	other threads:[~2015-09-17 15:56 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
2015-09-17 15:56                   ` Ivan Shapovalov [this message]
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=1442505391.4102.6.camel@gmail.com \
    --to=intelfx100@gmail.com \
    --cc=debian-boot@lists.debian.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=edward.shishkin@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).