linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Puttick <cputtick@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Practical partition/volume size limitation
Date: Tue, 9 Feb 2010 18:32:12 +0000	[thread overview]
Message-ID: <388f7e1a1002091032p633a7db4of269cccd4a8142bc@mail.gmail.com> (raw)

Hi all

Sorry to intrude and please feel free to redirect me to another more
appropriate list or alternative source (which I have been unable to
find). We're considering a large-scale filestore deployment (starting
with 32TB, single volume) and some team members have concerns about
the practical scalability of ext4 e.g. time to run fsck.

So some questions :)

Are there any examples of organisations running ext4 with large-scale
filestores? What sort of sizes? What issues, if any, have been
encountered? And if not ext4, what else (assuming a Linux preference)?

Thanks in advance.

Chris Puttick

-- 
My employers website: http://thehumanjourney.net - opinions in this
email are however very much my own and may not reflect that of my
current employer, past employers, associates, friends, family, pets etc..

Documents attached to this email may be in ISO 26300 format:
http://iso26300.info

                 reply	other threads:[~2010-02-09 18:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=388f7e1a1002091032p633a7db4of269cccd4a8142bc@mail.gmail.com \
    --to=cputtick@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).