From: Charles Marcus <CMarcus@Media-Brokers.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Question on compatibility with 2.6.31 kernel.
Date: Sat, 19 Sep 2009 14:20:19 -0400 [thread overview]
Message-ID: <4AB520E3.4080209@Media-Brokers.com> (raw)
In-Reply-To: <4AB3F3EE.5040004@candelatech.com>
On 9/18/2009, Ben Greear (greearb@candelatech.com) wrote:
> > 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.
>
> try to recompile kernel with
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
>
> (old lvm will not understand new sysfs design, this should
> provide old sysfs entries)
I'm also an lvm newbie, and since I'll obviously be running into this
sometime soon...
If lvm2 is updated first (before the kernel), I'm assuming it would
still be backward compatible with older kernels?
Or, if I updated the kernel first and compiled it with the above
options, when lvm2 gets updated, will I need to recompile the kernel
with the above options disabled before the next reboot?
Thanks,
--
Best regards,
Charles
next prev parent reply other threads:[~2009-09-19 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 19:25 [linux-lvm] Question on compatibility with 2.6.31 kernel Ben Greear
2009-09-18 19:48 ` 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 [this message]
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=4AB520E3.4080209@Media-Brokers.com \
--to=cmarcus@media-brokers.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 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).