From: Jim <jim@webstarts.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: install errors 3.2.0-rc4
Date: Tue, 06 Dec 2011 11:10:00 -0500 [thread overview]
Message-ID: <4EDE3E58.1030401@webstarts.com> (raw)
Good morning btrfs list,
I am trying to upgrade a remote server from kernel 3.1.0.rc4 to
3.2.0-rc4. I am not using make oldconfig. I use make menuconfig to do
a new configuration. After doing the dance of selecting (deselecting
actually) all includes and modules, I make sure I select btrfs to be
built in the kernel. The only place errors show up is in make install
where there are module not found errors. The most troubling is:
ERROR: modinfo: could not find module btrfs
Why is it even looking for this module when I specified to build btrfs
in the kernel. I would appreciate any thoughts, since this is a remote
server and any reboot issues involve much hassle with the colo service
team. The hardware this is being built on is dual quad-core xeons, 48Gb
memory 1ea 1Tb system disk and 12ea 1Tb disks on adaptec card to become
btrfs system. BTW, I am upgrading to pick up the latest patches as I
did have some exceptional latency when doing simple ls on the system. I
was testing with about 5.5Gb data on the btrfs system, in a file setup
involving thousands of subvolumes (replaced dirs with subvols for
snapshots).
Thanks
Jim Maloney
reply other threads:[~2011-12-06 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EDE3E58.1030401@webstarts.com \
--to=jim@webstarts.com \
--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;
as well as URLs for NNTP newsgroup(s).