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: Sun, 20 Sep 2015 17:10:50 +0300	[thread overview]
Message-ID: <1442758250.22253.4.camel@gmail.com> (raw)
In-Reply-To: <CAM12Q5SvTNm4XCycPgpP6cxiYWgtQx846JkSnYWvVQN=aNPNbA@mail.gmail.com>

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

On 2015-09-20 at 06:48 -0700, Jose R R wrote:
> On Thu, Sep 17, 2015 at 8:56 AM, Ivan Shapovalov <
> intelfx100@gmail.com> wrote:
> > 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:
> > > > > [...]
> > > > > 
> > > > > 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.
> > 
> I applied Ed's patch, as well
> < http://marc.info/?l=reiserfs-devel&m=144250028326153&w=2 >
> but the non-systemd Debian instance continued to generate a bad
> initrd.img-.
> 
> Notwithstanding, based on your suggestions, Ivan, the solution that
> works for non-systemd system is to include module directive
> crc32c_intel right *before* module reiser4 directive in debian's
> /etc/initramfs-tools/modules file, thus:
> [...]
> crc32c_intel
> reiser4
> [...]

Good. So, it's indeed lack of hard dependency between reiser4 and
crc32c that caused this error. There are softdeps, as Ben advised, but
indeed they are not taken into account by common initramfs building
tools.

I guess that this fact needs to be added to READMEs: one has to add
crc32c to their initramfs manually if one uses reiser4 on their root
partition and it is built as a module.

BTW, how is this solved in other filesystems which need some crypto or
checksum algorithms for their operation? Say, ext4?

-- 
Ivan Shapovalov / intelfx /


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

      reply	other threads:[~2015-09-20 14:10 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
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 [this message]

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=1442758250.22253.4.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).