public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: David Chinner <dgc@sgi.com>
Cc: Raz <raziebe@gmail.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: raid50 and 9TB volumes
Date: Tue, 17 Jul 2007 09:56:25 +1000	[thread overview]
Message-ID: <18076.1449.138328.66699@notabene.brown> (raw)
In-Reply-To: message from David Chinner on Tuesday July 17

On Tuesday July 17, dgc@sgi.com wrote:
> On Mon, Jul 16, 2007 at 04:53:22PM +0300, Raz wrote:
> > 
> > Well you are right.  /proc/partitions  says:
> > ....
> >   8   241  488384001 sdp1
> >   9     1 3404964864 md1
> >   9     2 3418684416 md2
> >   9     3 6823647232 md3
> > 
> > while xfs formats md3 as 9 TB.
> > If i am using LBD , what is the biggest size I can use on i386 ?
> 
> Supposedly 16TB. 32bit x 4k page size = 16TB. Given that the size is
> not being reported correctly, I'd say that this is probably not an
> XFS issue. The next thing to check is how large an MD device you
> can create correctly.
> 
> Neil, do you know of any problems with > 8TB md devices on i386?

Should work, but the amount of testing has been limited, and bugs
have existed.

Each component of a raid5 is limited to 2^32 K by the metadata, so
that is 4TB.  At 490GB, you are well under that.
There should be no problem with a 3TB raid5, providing LBD has been
selected.

raid0 over 3TB devices should also be fine.  There was a bug fixed in
May this year that caused problem with md/raid0 was used over
components larger than 4TB on a 32bit host, but that shouldn't affect
you and it does suggest that someone had success with a very large
raid0 once this bug was fixed.

If XFS is given a 6.8TB devices and formats it as 9TB, then I would be
looking at mkfs.xfs(??).

NeilBrown

  reply	other threads:[~2007-07-17  0:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 12:42 raid50 and 9TB volumes Raz
2007-07-16 13:01 ` David Chinner
2007-07-16 13:57   ` Raz
2007-07-16 15:24     ` Eric Sandeen
     [not found]   ` <5d96567b0707160653m5951fac9v5a56bb4c92174d63@mail.gmail.com>
2007-07-16 22:18     ` David Chinner
2007-07-16 23:56       ` Neil Brown [this message]
2007-07-17  0:12         ` David Chinner
2007-07-17  0:54           ` Neil Brown
2007-07-17  0:58             ` David Chinner
2007-07-23  6:09               ` Raz
2007-07-24  1:01                 ` David Chinner
2007-08-07  9:20                   ` Raz
2007-09-03 14:24                     ` Raz
2007-09-03 18:55                       ` Christian Kujau
2007-09-04  2:50                         ` Eric Sandeen

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=18076.1449.138328.66699@notabene.brown \
    --to=neilb@suse.de \
    --cc=dgc@sgi.com \
    --cc=raziebe@gmail.com \
    --cc=xfs@oss.sgi.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