All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Sandon Van Ness <sandon@van-ness.com>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: Is EXT4 the right FS for > 16TB?
Date: Sun, 19 Dec 2010 13:30:47 -0600	[thread overview]
Message-ID: <4D0E5D67.6060504@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1012191412520.27130@p34.internal.lan>

On 12/19/10 1:14 PM, Justin Piszcz wrote:
> 
> 
> On Sun, 19 Dec 2010, Eric Sandeen wrote:
> 
>> On 12/19/10 10:53 AM, Justin Piszcz wrote:
>>> Hi,
>>>
>>> Wow, there were no updates though after Eric's last comment..
>>> Eric, have there been any improvements in the past 6 months?
>>>
>>> Or should one still steer clear from EXT4 > 16TB?
>>
>> There is still no released e2fsprogs which supports > 16T for
>> ext4, but testing of the not-released bits is welcomed...
>> Ted says a 16T-capable version is coming soon.  There's still
>> work to be done there, though.
>>
>> -Eric
>>
> 
> Thanks Eric for confirming.
> 
> With 7 x 3TB HDD its now possible to breach 16TB (16.38TB) in RAID-5 so I
> suppose more people may start asking about this.

Agreed, 16T is not that much these days.

As Ric said, XFS will handle it without problem, though.

-Eric

> Justin.
> 


  reply	other threads:[~2010-12-19 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 11:52 Is EXT4 the right FS for > 16TB? Justin Piszcz
2010-12-19 16:35 ` Sandon Van Ness
2010-12-19 16:53   ` Justin Piszcz
2010-12-19 17:01     ` Eric Sandeen
2010-12-19 17:14       ` Ric Wheeler
2010-12-19 19:14       ` Justin Piszcz
2010-12-19 19:30         ` Eric Sandeen [this message]
2010-12-19 22:21           ` Ric Wheeler

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=4D0E5D67.6060504@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandon@van-ness.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 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.