linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Sandon Van Ness <sandon@van-ness.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Is >16TB support considered stable?
Date: Fri, 28 May 2010 15:39:24 -0400	[thread overview]
Message-ID: <4C001BEC.9080906@redhat.com> (raw)
In-Reply-To: <4BFFF4D2.6020908@van-ness.com>

On 05/28/2010 12:52 PM, Sandon Van Ness wrote:
> I have a 36 TB (33.5276 TiB) device. I was originally planning to run
> JFS like I am doing on my 18 TB (16.6697 TiB) partition but the
> userspace tools for file-system creation (mkfs) on JFS do not correctly
> create file-systems over 32 TiB. XFS is not an option for me (I have had
> bad experiences and its too corruptible) and btrfs is too beta for me.
> My only options thus are ext4 or JFS (limited to 32 TiB).
>
> I would rather not waste ~ 1TiB of space which will likely go to other
> partitions that would normally only be 500 GiB but will now be 1.5 TiB
> if I can and with some of my testing of ext4 I think it could be a
> viable solution. I heard that with the pu branch 64-bit addressing
> exists so you can successfully create/fsck>16 TiB file-systems. I did
> read on the mailing lists that there were some problems on 32-bit
> machine but i will only use this file-sytem on x86_64.
>
> So here is my question to you guys:
>
> Is the pu branch pretty stable? Is it stable enough to have a 33 TiB
> file-system in the real-world and be as stable and work as well as a<16
> TiB file-system or am I better off losing out some of my space and
> making a 32 TiB (minus a little) JFS partition and just stick to what I
> know works and works well?
>    

Not sure which version of XFS you had trouble with, but it is certainly 
the most stable file system for anything over 16TB....

Regards,

Ric


  reply	other threads:[~2010-05-28 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28 16:52 Is >16TB support considered stable? Sandon Van Ness
2010-05-28 19:39 ` Ric Wheeler [this message]
2010-05-29  2:47   ` Sandon Van Ness
2010-05-29  4:32     ` Stewart Smith
2010-05-29 20:40       ` Sandon Van Ness
2010-06-01 14:18         ` Ric Wheeler
2010-06-01 16:30           ` 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=4C001BEC.9080906@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=linux-ext4@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 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).