From: Ben Greear <greearb@candelatech.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Question on compatibility with 2.6.31 kernel.
Date: Fri, 18 Sep 2009 12:25:02 -0700 [thread overview]
Message-ID: <4AB3DE8E.9080301@candelatech.com> (raw)
Hello!
I recently tried to boot 2.6.31 on Fedora 8, and it couldn't
find the volume groups. The same kernel works fine on F11.
Someone on LKML said they had similar problems on an old Debian Etch
system and to fix it they installed a new version of lvm2 and put
that in the initrd.
I am trying to package a general purpose 2.6.31, and part of the install
logic is to run mkinitrd on the end-user's system, so it will be a big
pain to also require users to install a non-standard lvm for their
platform.
So, does anyone have any ideas about what incompatibily I might be hitting,
and perhaps have some ideas on how to fix it in the kernel so that new
kernels will boot with older lvm installs?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2009-09-18 19:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 19:25 Ben Greear [this message]
2009-09-18 19:48 ` [linux-lvm] Question on compatibility with 2.6.31 kernel Milan Broz
2009-09-18 20:47 ` [linux-lvm] Disk crash on LVM Fredrik Skog
2009-09-18 21:19 ` Ray Morris
2009-09-18 21:31 ` Stuart D. Gathman
2009-09-18 21:55 ` Ray Morris
2009-09-19 14:11 ` André Gillibert
2009-09-19 17:45 ` Fredrik Skog
2009-09-21 11:27 ` Peter Keller
2009-09-22 13:27 ` Fredrik Skog
2009-09-22 13:43 ` Fredrik Skog
2009-09-22 15:54 ` Fredrik Skog
2009-09-22 16:11 ` Alasdair G Kergon
2009-09-18 20:56 ` [linux-lvm] Question on compatibility with 2.6.31 kernel Ben Greear
2009-09-19 18:20 ` Charles Marcus
2009-09-19 22:17 ` André Gillibert
2009-09-20 8:12 ` Milan Broz
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=4AB3DE8E.9080301@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-lvm@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.