From: Ragnar =?unknown-8bit?Q?Kj=F8rstad?= <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] [Q] patch to overcome 2TB block device limit?
Date: Fri May 9 19:22:02 2003 [thread overview]
Message-ID: <20030510002217.GE16354@vestdata.no> (raw)
In-Reply-To: <20030509194249.GB6189@localhost>
On Fri, May 09, 2003 at 09:42:49PM +0200, Jose Luis Domingo Lopez wrote:
> On Friday, 09 May 2003, at 18:29:46 +0900,
> A. S. wrote:
> > Is there any kernel patches to exceed the 2TB kernel block device limit ?
> > I want to be able to create about single 5TB LV.
> >
> Yes, and it has been in mainline 2.5.x kernels for a while now. Do a
> "make menuconfig" and under "Block devices" the last option is
> "[ ] Support for Large Block Devices". From the help:
>
> x CONFIG_LBD: x
But does it support > 2 GB LVM logical volumes too now, or just > 2GB md-
devices like it used to?
--
Ragnar Kjørstad
Zet.no
prev parent reply other threads:[~2003-05-09 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 4:32 [linux-lvm] [Q] patch to overcome 2TB block device limit? A. S.
2003-05-09 14:42 ` Jose Luis Domingo Lopez
2003-05-09 19:22 ` Ragnar =?unknown-8bit?Q?Kj=F8rstad?= [this message]
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=20030510002217.GE16354@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox