From: Matthew Wilcox <matthew@wil.cx>
To: Drew <drew.kay@gmail.com>
Cc: Tomasz Torcz <tomek@pipebreaker.pl>, linux-scsi@vger.kernel.org
Subject: Re: can't access LUN >2TB with aic7xxx, Infortrend EonStor and 2.6.31-rc1
Date: Mon, 29 Jun 2009 07:47:39 -0600 [thread overview]
Message-ID: <20090629134739.GO5480@parisc-linux.org> (raw)
In-Reply-To: <c268e4660906290640k3364aeaey30d37b884a2ce1c6@mail.gmail.com>
On Mon, Jun 29, 2009 at 06:40:21AM -0700, Drew wrote:
> > You could also go for a configuration fix where you reconfigure the array
> > with LUNs below 2TB and then use MD or DM to stitch them back together
> > into a single device.
>
> Would you not also have to partition the drive using GPT partitions?
> LVM aside, I thought any partition over 2TB had to be GPT.
If you choose to partition the device at all -- I often create filesystems
directly on the block device. Regardless, you need the SCSI command
to be able to get to the device before you can start worrying about
partitioning schemes.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-06-29 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 13:08 can't access LUN >2TB with aic7xxx, Infortrend EonStor and 2.6.31-rc1 Tomasz Torcz
2009-06-29 13:34 ` Matthew Wilcox
2009-06-29 13:40 ` Drew
2009-06-29 13:47 ` Matthew Wilcox [this message]
2009-06-29 14:54 ` Drew
2009-06-29 13:46 ` Matthew Wilcox
2009-06-29 16:13 ` Tomasz Torcz
2009-06-30 9:40 ` Tomasz Torcz
2009-06-30 14:45 ` James Bottomley
2009-06-30 15:48 ` James Bottomley
2009-07-01 6:10 ` Tomasz Torcz
2009-07-01 14:19 ` James Bottomley
2009-06-29 14:33 ` James Bottomley
2009-06-29 14:56 ` Matthew Wilcox
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=20090629134739.GO5480@parisc-linux.org \
--to=matthew@wil.cx \
--cc=drew.kay@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tomek@pipebreaker.pl \
/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.