From: Wolfgang Sailer <Wolfgang@Sailer.priv.at>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS on a block device > 2TB: will it work?
Date: Sat, 02 Jan 2010 18:23:31 +0100 [thread overview]
Message-ID: <4B3F8113.5030408@Sailer.priv.at> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear all!
Question: Will I be able to use a block device >2TB as the target of LUKS?
Background:
I have a setup in which I mdadm-raid5-ed 3 1TB drives into a /dev/mdN of
1.998 TB in size. On this mdadm array I created a LVM, and one of the LVs
living there is 1.2 TB in size (/dev/mapper/VG/LV-LUKS) and serves as a
block-device for LUKS.
I would like to add another 1TB drive to the array and add the additional
space to the LUKS device. My i386 kernel 2.6.24 configuration has LBD
enabled (pushing the usual 2TB limit typical of a 32bit OS to 16TB), so
mdadm should be able to expand the array to 3TB and I believe also LVM2
should be able to use 3TB of space and be able to expand the LV to 2.2TB.
What I am not sure of is whether LUKS can make use of a 2.2TB blockdevice or
if there will be a 2TB limit somewhere due to some
WORD/INT/LONGINT/LONGLONGINT variable somwhere in the LUKS-code.
ext3, again, is able to create filesystems >2TB, so that should be fine.
regards, Wolfgang
- --
Charlie Chaplin hat einmal auf einem
Charlie Chaplin Doppelgänger Wettbewerb
in Monte Carlo den 3. Platz erreicht.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFLP4ETR6b2EdogPFsRAu9sAKC7gmI4djZsKqqYZ0AUvWA0bFrrTACeJNjE
3qOweb0AqKzH1AxyLFftiQ0=
=jBh/
-----END PGP SIGNATURE-----
next reply other threads:[~2010-01-02 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 17:23 Wolfgang Sailer [this message]
2010-01-02 20:07 ` [dm-crypt] LUKS on a block device > 2TB: will it work? 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=4B3F8113.5030408@Sailer.priv.at \
--to=wolfgang@sailer.priv.at \
--cc=dm-crypt@saout.de \
/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