All of lore.kernel.org
 help / color / mirror / Atom feed
From: jmerkey <jmerkey@utah-nac.org>
To: Andreas Dilger <adilger@shaw.ca>
Cc: Dan Stromberg <strombrg@dcs.nac.uci.edu>, linux-kernel@vger.kernel.org
Subject: Re: huge filesystems
Date: Mon, 14 Mar 2005 09:56:49 -0700	[thread overview]
Message-ID: <4235C251.7000801@utah-nac.org> (raw)
In-Reply-To: <20050314164137.GC1451@schnapps.adilger.int>


I am running the DSFS file system as a 7 TB file system on 2.6.9. There 
are a host
of problems with the current VFS, ad I have gotten around most of them 
by **NOT** using the linux page cache interface. The VFS I am using 
creates a virtual represeation of the files and it's own cache. You need 
a lot of memory - 2GB roughly. The only way to do it at present is to 
use the address patch that reserves 1GB for user address space and 
leaves 3GB of space
in kernel in order to create the caches.

You also need to ignore the broken fdisk partitioning tools. Just create 
one partition if you
create disks larger than 2 TB with 3Ware, and ignore the values in the 
table. I check for a single partition on these devices and rely on the 
capacity parameter reported from the
bdev handle and just use the extra space.

Linux proper has a long way to go on this topic, but it is possible I am 
doing this today
on 2.6.9.

Jeff



  reply	other threads:[~2005-03-14 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 18:53 huge filesystems 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 [this message]
2005-03-15  3:21     ` Andrew Morton
2005-03-15  3:37       ` jmerkey
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=4235C251.7000801@utah-nac.org \
    --to=jmerkey@utah-nac.org \
    --cc=adilger@shaw.ca \
    --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 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.