Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: linux-btrfs@vger.kernel.org
Subject: btrfs module dependencies broken in 3.14?
Date: Fri, 6 Jun 2014 20:40:09 +0600	[thread overview]
Message-ID: <20140606204009.261e8ec3@natsu> (raw)

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

Hello,

Not sure if this has been reported somewhere closer to Btrfs development, and
not just in Debian... Anyways, just now I (also) hit this bug when upgrading my
kernel from 3.12.21 to 3.14.5 on one machine (but not on a number of others):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747929

I use btrfs as my root FS, and the error early in the initramfs stage, is
along the lines of:

> FATAL: Error inserting btrfs...: Unknown symbol in 
> module, or unknown parameter (see dmesg)

(noting in dmesg).

The workaround has been detailed back in 2010:
https://lists.debian.org/debian-user/2010/06/msg02060.html

After adding "crc32c" into /etc/initramfs-tools/modules (for forced inclusion
into the initramfs) and regenerating the initramfs image, the btrfs module
started loading fine.

Interesting why this problem from 2010 has resurfaced in 3.14, with 3.12
working normally. Also why not every machine with a similar setup is affected
(I have several hosts with btrfs root, although both hardware and software
configurations are not identical but quite diverse), but as I said just one
for me.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2014-06-06 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 14:40 Roman Mamedov [this message]
2014-06-06 15:41 ` btrfs module dependencies broken in 3.14? Filipe David Manana
2014-06-06 18:31   ` WorMzy Tykashi
2014-06-06 18:53     ` Roman Mamedov
2014-06-06 20:05       ` WorMzy Tykashi

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=20140606204009.261e8ec3@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@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