From: Ramon van Alteren <ramon@vanalteren.nl>
To: nfs@lists.sourceforge.net
Cc: Chris Penney <penney@msu.edu>
Subject: Re: Writing to an NFS share truncates files on >8Tb Raid + LVM2
Date: Wed, 22 Feb 2006 14:15:33 +0100 [thread overview]
Message-ID: <43FC63F5.6090809@vanalteren.nl> (raw)
In-Reply-To: <43FC6252.2030104@vanalteren.nl>
Ramon van Alteren wrote:
> Anybody any experience with ext3 on filesystems >8Tb.
> Chikama pointed me to the explanation on why this doesn't work with
> reiserfs.
>
> But now I need to figure out which filesystem I will use.
> Testing reveals that ext3 is pretty fast:
> http://linuxgazette.net/122/piszcz.html
> However I have no clue how ext3 behaves with >8Tb filesystems.
Nevermind....
Should learn to sit on fingers longer. From the ext3 faq:
Q: What is the largest possible size of an ext3 filesystem and of
files on ext3?
inspired by Andreas Dilger, suggested by Christian Kujau:
Ext3 can support files up to 1TB. With a 2.4 kernel the filesystem size
is limited by the maximal block device size, which is 2TB. In 2.6 the
maximum (32-bit CPU) limit is of block devices is 16TB, but ext3
supports only up to 4TB.
Ramon
--
To be stupid and selfish and to have good health are the three requirements for happiness, though if stupidity is lacking, the others are useless.
Gustave Flaubert
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-02-22 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 10:37 Writing to an NFS share truncates files on >8Tb Raid + LVM2 Ramon van Alteren
2006-02-22 10:45 ` CHIKAMA masaki
[not found] ` <111aefd0602220459s1786fe4ewddc5c21698002e27@mail.gmail.com>
2006-02-22 13:08 ` Ramon van Alteren
2006-02-22 13:15 ` Ramon van Alteren [this message]
2006-02-22 13:41 ` Chris Penney
-- strict thread matches above, loose matches on Subject: below --
2006-02-21 15:30 Ramon van Alteren
2006-02-21 22:55 ` Lee Revell
2006-02-22 10:30 ` Ramon van Alteren
2006-02-22 17:36 ` Andi Kleen
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=43FC63F5.6090809@vanalteren.nl \
--to=ramon@vanalteren.nl \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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.