linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "bmoon" <bo@anthologysolutions.com>
To: "Peter L. Ashford" <ashford@sdsc.edu>
Cc: Stephan van Hienen <raid@a2000.nu>,
	Donghui Wen <dhwen@protegonetworks.com>,
	linux-raid@vger.kernel.org
Subject: Re: maximum disk capacity?
Date: Fri, 13 Jun 2003 14:33:46 -0700	[thread overview]
Message-ID: <018701c331f3$79ab76c0$6b01a8c0@bmoon> (raw)
In-Reply-To: Pine.GSO.4.30.0306131032590.1148-100000@multivac.sdsc.edu

My question is from  Stephan van Hienen's email;

"
         if you need to go above to 2TB, you need the largedisk patch
         which doesn't work with sw raid5 (so no 2TB+ with sw raid5)

          i'm running with 13*180GB (+1 Hotspare) in sw raid5 (hd's
         connected to 2*3ware 7850)
"

What is the reason why it can not work with SW raid5 even with the largedisk
patch???



----- Original Message -----
From: "Peter L. Ashford" <ashford@sdsc.edu>
To: "bmoon" <bo@anthologysolutions.com>
Cc: "Stephan van Hienen" <raid@a2000.nu>; "Donghui Wen"
<dhwen@protegonetworks.com>; <linux-raid@vger.kernel.org>
Sent: Friday, June 13, 2003 10:39 AM
Subject: Re: maximum disk capacity?


> > What is the reason that it can not cover more than 2TB?
>
> A 32-bit block number with 512-byte blocks.  This multiplies out to 2TB.
>
> > By the way you are able to use more than 2TB, ~2.3TB???
> > Why?
>
> 2TB binary is 2.2TB decimal (2,199,023,255,552).  You shouldn't be able to
> get 2.3TB without the patch.
>
> > > > Hi, I am setting up hardware raid with 7 harddrives on redhat linux.
> > > > I use 3ware + hardware raid 5, each harddrive is 200G. For
> > > > linux, this raid sould act as a 1.2TB scsi hard drive. But it seems
> > > > redhat could not reconize it. I am wondering may be a 1.2TB hard
drive
> > > > is too large to linux. So my question is: what't
> > > > the maxium disk capacity Linux can support?
>
> There is a problem with the RedHat installation scripts.  When performing
> a Kickstart install, and using the Grub boot loader, disks are limited to
> 1TB (binary).  Is this the problem you encountered?
>
> Good luck.
> Peter Ashford
>
>


  parent reply	other threads:[~2003-06-13 21:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12  8:08 Crashing a software raid 5 partition ( disk trouble ) Nicolas Meaux
2003-06-12 10:26 ` Martin Hermanowski
2003-06-12 10:29 ` Neil Brown
2003-06-12 10:35   ` Neil Brown
2003-06-12 10:06     ` Nicolas Meaux
2003-06-12 16:14       ` Bernd Schubert
2003-06-12 23:49         ` maximum disk capacity? Donghui Wen
2003-06-13  7:51           ` Stephan van Hienen
2003-06-13 17:21             ` bmoon
2003-06-13 17:39               ` Peter L. Ashford
2003-06-13 17:58                 ` Donghui Wen
2003-06-13 21:33                 ` bmoon [this message]
2003-06-14  7:16                   ` Stephan van Hienen
2003-06-14  7:15               ` Stephan van Hienen
2003-06-13  5:31       ` Crashing a software raid 5 partition ( disk trouble ) Neil Brown

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='018701c331f3$79ab76c0$6b01a8c0@bmoon' \
    --to=bo@anthologysolutions.com \
    --cc=ashford@sdsc.edu \
    --cc=dhwen@protegonetworks.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=raid@a2000.nu \
    /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).