From: christian e <cej@ti.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] which kernel would you recommend ??
Date: Mon Oct 22 09:52:02 2001 [thread overview]
Message-ID: <3BD432EE.76993E30@ti.com> (raw)
In-Reply-To: 3BD40062.2D93A980@ti.com
christian e wrote:
>
> Hi,all
>
> I've been trying for some days now to get lvm installed on a 2.4
> kernel..Has not been very successful to say the least.What kernel would
> you recommend for a production file-server ?? Should I go back to 2.2.19
> again ?? I upgraded to 2.4 due to NFS and ext3 mainly.It also has the
> latest drivers for my megaraid controllers.But now I can't get lvm
> compiled ..Is 2.4 even stable enough to use in production ? Can't allow
> this server to be down as it's our primary fil-server..
Never mind.Down to 2.2.19 again and everything works now..Guess I'll
keep it here for the time being..
best regards
Christian
next prev parent reply other threads:[~2001-10-22 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 6:16 [linux-lvm] which kernel would you recommend ?? christian e
2001-10-22 9:52 ` christian e [this message]
2001-10-22 10:14 ` Patrick Boutilier
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=3BD432EE.76993E30@ti.com \
--to=cej@ti.com \
--cc=linux-lvm@sistina.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).