From: Tejun Heo <tj@kernel.org>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
opensuse@opensuse.org
Subject: Re: [opensuse] Seeking advice: 4TB external drive
Date: Wed, 20 Aug 2008 17:08:08 +0900 [thread overview]
Message-ID: <48ABD0E8.2010104@kernel.org> (raw)
In-Reply-To: <87f94c370808150546rfd6468er8503176bef0cf9b7@mail.gmail.com>
Greg Freemyer wrote:
> On Thu, Aug 14, 2008 at 11:11 PM, Philip Warner <pjw@rhyme.com.au> wrote:
>> Sandy Drobic wrote:
>>> If you really intend to use an external drive larger than 1 TB you
>>> should definitely plan to use at least gigabit ethernet or eSATA.
>>> Anything else doesn't make much sense with storage of that size.
>> Yeah; that was the original plan until I failed to find an eSATA card
>> that would cope with a 4TB external disk. The last one I bought was
>> supposed to be 48bit LBA throughout, but the disk still shows up as the
>> wrong size in the cards internal bios (1.8TB). Using USB frightens me
>> considerably since I have (historically) had a great deal of trouble
>> getting large external USB drived to function reliably under linux. And,
>> as you say, they are slooow.
>>
>> If I go eSATA, it omes back to the hardware question: anyone know of a
>> hardware/software combo that thy know can cope with a single 4TB eSATA
>> drive?
>>
>> Also, maybe this is no longer a SuSE uestion.
>
> Agreed, not a suse question. If you are now thinking eSata, you
> should ask on the linux kernel sata list.
If you're not gonna boot off the drive, what the BIOS thinks is
irrelevant although I wonder whether the 1.8TB limit comes from. 1.8TB
doesn't really fall on 2^n boundary. Although for some reason the BIOS
used 32bit number to address LBAs it will only be able to address upto
2TiB which is sort of kind of in the vicinity of the ballpark if you
stretch it just right. :-P
Anyways, once the system is up and running, I think it should be just
fine. There definitely isn't a limit in the software stack and most
modern controllers should be fine with it too. There just isn't much
reason to choke on that boundary. The BIOS might enable HPA to limit
the drive size to something it can handle but libata.ignore_hpa=1 will
make libata unlock it (which is the default on certain distros including
SUSE).
--
tejun
prev parent reply other threads:[~2008-08-20 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A39DF3.2030105@rhyme.com.au>
[not found] ` <87f94c370808140605w6d7af3c4nc75de67377cfc3ae@mail.gmail.com>
[not found] ` <48A44995.2010908@rhyme.com.au>
[not found] ` <48A45957.6060300@japantest.homelinux.com>
[not found] ` <48A4F3CB.5060204@rhyme.com.au>
2008-08-15 12:46 ` [opensuse] Seeking advice: 4TB external drive Greg Freemyer
2008-08-20 8:08 ` Tejun Heo [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=48ABD0E8.2010104@kernel.org \
--to=tj@kernel.org \
--cc=greg.freemyer@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=opensuse@opensuse.org \
/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;
as well as URLs for NNTP newsgroup(s).