From: James Smart <James.Smart@Emulex.Com>
To: lkml@foss.daxal.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fibre channel network interfaces + Linux SAN
Date: Tue, 18 Mar 2008 17:16:28 -0400 [thread overview]
Message-ID: <47E0312C.3040805@emulex.com> (raw)
In-Reply-To: <47E01DB3.90307@emulex.com>
Scott,
Re: IP networking on FC
It is possible, and Emulex has had product in the past for this. However, we've
never had enough interest to warrant the work needed to get it up on 2.6.
In general, there's very little interest in it anymore.
Re: LVM on FC
The LVM on FC scsi disks should be normal. The more interesting part is the boot
part. Boot support means getting the expansion rom driver configured properly
(whether that be BIOS, EFI, or OpenBoot). If you go to the Emulex support/download
page, and look for firmware for your adapter, there is documentation on the setting
boot devices, etc. You will need to be careful that the disk is either used on its
own or as a mirror, it can't be used as a raid set. Further boot specifics should
defer to grub (or your favorite boot loader) and LVM. Outside the expansion rom
driver setup, the fact that it's FC should not matter, and it should look like a
normal scsi disk. And now the bad news... the LP8000 is rather old, it may be EOL'd,
so you may not find the latest boot firmware, and you would be stuck with whatever
is on the adapter, or find a newer one.
-- james s
Scott Edwards wrote:
> Two things I'm trying to solve with my fc hardware. How do I enable these
> for IP networking, and how do I offer say lvm logical volumes behind Linux
> as a SAN? I'd like nodes to be bootable and offer specific volumes as their
> disks. I'm using 2.6.28
next parent reply other threads:[~2008-03-19 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47E01DB3.90307@emulex.com>
2008-03-18 21:16 ` James Smart [this message]
2008-03-17 14:18 Fibre channel network interfaces + Linux SAN Scott Edwards
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=47E0312C.3040805@emulex.com \
--to=james.smart@emulex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@foss.daxal.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