public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: david@lang.hm
Cc: xfs@oss.sgi.com
Subject: Re: 128TB filesystem limit?
Date: Fri, 26 Mar 2010 10:54:33 +1100	[thread overview]
Message-ID: <20100325235433.GM3335@dastard> (raw)
In-Reply-To: <alpine.DEB.2.00.1003251609160.12435@asgard.lang.hm>

On Thu, Mar 25, 2010 at 04:15:42PM -0700, david@lang.hm wrote:
> I'm working with a raid 0 (md) array on top of 10 16x1TB raid 6
> hardware arrays.
> 
> fdisk -l shows me 10 drives like
> 
> WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util
> fdisk doesn't support GPT. Use GNU Parted.
> 
> 
> Disk /dev/sdk: 13999.9 GB, 13999999025152 bytes
> 255 heads, 63 sectors/track, 1702069 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x00000000
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdk1               1      267350  2147483647+  ee  EFI GPT
> 
> and then the md0 device as
> 
> Disk /dev/md0: 139999.9 GB, 139999989596160 bytes
> 2 heads, 4 sectors/track, -1 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Disk identifier: 0x00000000
> 
> Disk /dev/md0 doesn't contain a valid partition table
> 
> 
> I then did mkfs.xfs /dev/md0
> 
> but a df is showing me 128TB

What is in /proc/partitions?

> is this just rounding error combined with the 1000=1k vs 1024=1k
> marketing stuff,

Probably.

> or is there some limit I am bumping into here.

Unlikely to be an XFS limit - I was doing some "what happens if"
testing on multi-PB sized XFS filesystems hosted on sparse files
a couple of days ago....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-03-25 23:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 23:15 128TB filesystem limit? david
2010-03-25 23:54 ` Dave Chinner [this message]
2010-03-26  0:03   ` david
2010-03-26  0:35     ` Dave Chinner
2010-03-26  2:02       ` david
2010-03-26  4:35         ` Eric Sandeen
2010-03-26  4:56           ` david
2010-03-26  6:09             ` Stan Hoeppner
2010-03-26  7:26             ` Steve Costaras
2010-03-27  9:06 ` Emmanuel Florac
2010-03-27 14:28   ` Steve Costaras
2010-03-27 18:45   ` david
2010-03-28 21:17 ` Peter Grandi

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=20100325235433.GM3335@dastard \
    --to=david@fromorbit.com \
    --cc=david@lang.hm \
    --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