From: jmerkey <jmerkey@utah-nac.org>
To: Andrew Morton <akpm@osdl.org>
Cc: adilger@shaw.ca, strombrg@dcs.nac.uci.edu, linux-kernel@vger.kernel.org
Subject: Re: huge filesystems
Date: Mon, 14 Mar 2005 20:37:34 -0700 [thread overview]
Message-ID: <4236587E.5060200@utah-nac.org> (raw)
In-Reply-To: <20050314192140.1b3680da.akpm@osdl.org>
Andrew Morton wrote:
>jmerkey <jmerkey@utah-nac.org> wrote:
>
>
>>I am running the DSFS file system as a 7 TB file system on 2.6.9.
>>
>>
>
>On a 32-bit CPU?
>
>
Yep.
>
>
>>There are a host of problems with the current VFS,
>>
>>
>
>I don't recall you reporting any of them. How can we expect to fix
>anything if we aren't told about it?
>
>
>
I report them when I can't get around them myself. I've been able to get
around most of them.
>>ad I have gotten around most of them
>> by **NOT** using the linux page cache interface.
>>
>>
>
>Well that won't fly.
>
>
>
>
For this application it will.
>The VFS should support devices up to 16TB on 32-bit CPUs. If you know of
>scenarios in which it fails to do that, please send a bug report.
>
>
>
>
Based on the changes I've mode to it locally for my version of 2.6.9, it
now goes to
1 zetabyte (1024 pedabytes). Largest one I've configured so far with
actual storage
is 128 TB, though. Had to drop the page cache and replace though -- for now.
Jeff
next prev parent reply other threads:[~2005-03-15 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 18:53 Dan Stromberg
2005-03-09 19:37 ` Chris Wedgwood
2005-03-09 22:01 ` Miklos Szeredi
2005-03-14 16:41 ` Andreas Dilger
2005-03-14 16:56 ` jmerkey
2005-03-15 3:21 ` Andrew Morton
2005-03-15 3:37 ` jmerkey [this message]
2005-03-15 4:02 ` Andrew Morton
2005-03-15 4:37 ` jmerkey
2005-03-15 6:04 ` Andreas Dilger
2005-03-19 11:06 ` Eric W. Biederman
2005-03-15 9:28 ` Barry K. Nathan
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=4236587E.5060200@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=adilger@shaw.ca \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=strombrg@dcs.nac.uci.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®