From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] FW: LVM on Linux
Date: Mon, 16 Jul 2001 23:10:25 +0200 [thread overview]
Message-ID: <20010716231024.I14564@vestdata.no> (raw)
In-Reply-To: <85063BBE668FD411944400D0B744267A643418@AUSMAIL>; from Gonyou, Austin on Mon, Jul 16, 2001 at 03:42:00PM -0500
On Mon, Jul 16, 2001 at 03:42:00PM -0500, Gonyou, Austin wrote:
> I think ELVM at the bottom is EVMS. I wish I knew where the original article
> was, cause I'd like to know what 64bit frame he's talking about. Currently
> I'm using LVM for striping, and plan to use it with Fibre. From what I
> understand on this list, is that others are using it on fibre already. So,
> if they are using a 2.4 kernel, with fibre, wouldn't that mean that they'd
> need to employ 64-bit access(if they use a 64-bit controller+driver?)
I'm not sure what you mean here.
The 32/64 bit question in this thread was the datatype used to store
sector-numbers; the effect of using 32bit is that it limits the
device-size to 1 (2) TB.
If you're talking about 64 bit PCI busses and such; this is totally
unrelated.
And yes, we'd like to use LVM on FibreChannel devices, and need 64 bit
sector numbers :)
--
Ragnar Kjorstad
Big Storage
next prev parent reply other threads:[~2001-07-16 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 20:42 [linux-lvm] FW: LVM on Linux Gonyou, Austin
2001-07-16 21:10 ` Ragnar Kjørstad [this message]
2001-07-17 16:40 ` Joe Thornber
2001-07-17 18:10 ` Ragnar Kjørstad
2001-07-17 19:23 ` Ralph Jennings
2001-07-18 8:16 ` Joe Thornber
2001-07-18 15:01 ` Heinz J. Mauelshagen
2001-07-18 16:58 ` Steven Lembark
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 23:26 Gonyou, Austin
2001-07-16 23:58 ` Ragnar Kjørstad
2001-07-16 20:35 Gonyou, Austin
2001-07-17 11:27 ` Heinz J. Mauelshagen
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=20010716231024.I14564@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--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 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.