From: Goswin von Brederlow <goswin-v-b@web.de>
To: rwheeler@redhat.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 64bit (disk >16TB) question
Date: Tue, 15 Jul 2008 18:13:18 +0200 [thread overview]
Message-ID: <87tzer9lcx.fsf@frosties.localdomain> (raw)
In-Reply-To: <487CAF6A.8070403@redhat.com> (Ric Wheeler's message of "Tue, 15 Jul 2008 10:08:42 -0400")
Ric Wheeler <rwheeler@redhat.com> writes:
> How long would you wait for something like fsck to run to completion
> before you would need to go to back up tapes? 6 hours? 1 day? 1 week
> ;-) ?
Backup? What are backups? :))
A hardware raid6 resync takes about 16h. A Software raid6 (over 6
hardware raid6) resync takes 1-2 days.
With lustre the fsck has to be done on the MDT (meta data target) to
build a database file and on all the OST (object storage target). So
there is some parallelization in the system.
But each OST, if we get ext4 64bit working, would be 28TB. I would
assume days for an fsck run. Weeks would not be good and less than a
day is totaly unrealistic.
But a few days for an fsck of 400-800TB filesystem isn't so
bad. Reading that amount from backup will take ages too, if you even
have one.
MfG
Goswin
next prev parent reply other threads:[~2008-07-15 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:50 ext4 64bit (disk >16TB) question Goswin von Brederlow
2008-07-14 23:46 ` Theodore Tso
2008-07-15 5:42 ` Goswin von Brederlow
2008-07-15 12:36 ` Theodore Tso
2008-07-15 17:00 ` Goswin von Brederlow
2008-07-15 17:19 ` Theodore Tso
2008-07-15 13:16 ` Ric Wheeler
2008-07-15 14:01 ` Bernd Schubert
2008-07-15 14:08 ` Ric Wheeler
2008-07-15 16:13 ` Goswin von Brederlow [this message]
2008-07-15 18:27 ` Jose R. Santos
2008-07-15 20:12 ` Andreas Dilger
2008-07-15 20:15 ` Ric Wheeler
2008-07-15 21:03 ` Goswin von Brederlow
2008-07-15 21:20 ` Jose R. Santos
2008-07-16 10:10 ` Goswin von Brederlow
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=87tzer9lcx.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.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