From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: james.rich@m.cc.utah.edu, Tom Sightler <ttsig@tuxyturvy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Questions about Enterprise Storage with Linux
Date: Thu, 8 Mar 2001 07:37:51 -0600 (CST) [thread overview]
Message-ID: <200103081337.HAA76233@tomcat.admin.navo.hpc.mil> (raw)
james rich <james.rich@m.cc.utah.edu>:
> On Wed, 7 Mar 2001, Tom Sightler wrote:
>
> > 2. Does linux have any problems with large (500GB+) NFS exports, how about
> > large files over NFS?
> >
> > 3. What filesystem would be best for such large volumes? We currently use
> > reirserfs on our internal system, but they generally have filesystems in the
> > 18-30GB ranges and we're talking about potentially 10-20x that. Should we
> > look at JFS/XFS or others?
>
> I think that for filesystems this size you definately want to look at XFS
> of JFS. Maybe you will decide not to use them - but you should test them.
>
> I am currently using XFS and it really works. It currently has some
> issues when used with raid 1, but it is probably the most suited for what
> you want. Exporting an XFS volume over NFS is no problem. You can also
> use xfs_growfs to change the size of your XFS partition. I haven't had
> any instability during all the time I've used XFS.
The biggest difficulty I had with XFS (not on linux as a server) had
more to do with NFS/XFS performance. The SGI clients worked fine while
the Linux clients were about 10-20% slower. This was a year ago so this
may not apply anymore. I haven't seen any Linux NFS benchmarks recently.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2001-03-08 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 13:37 Jesse Pollard [this message]
2001-03-08 16:48 ` Questions about Enterprise Storage with Linux james rich
[not found] <Pine.LNX.4.21.0103090725030.699-100000@penguin.homenet>
2001-03-09 7:37 ` Tigran Aivazian
2001-03-09 17:30 ` Jauder Ho
-- strict thread matches above, loose matches on Subject: below --
2001-03-07 23:13 Linux 2.4.2ac14 Alan Cox
2001-03-08 0:40 ` Greg KH
2001-03-08 0:17 ` Questions about Enterprise Storage with Linux Tom Sightler
2001-03-08 2:11 ` Jesse Pollard
2001-03-08 1:20 ` Marcelo Tosatti
2001-03-08 2:35 ` Tom Sightler
2001-03-08 6:00 ` Tim Moore
2001-03-08 5:09 ` Jauder Ho
2001-03-08 7:22 ` james rich
2001-03-09 0:29 ` Thomas Davis
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=200103081337.HAA76233@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=james.rich@m.cc.utah.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.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;
as well as URLs for NNTP newsgroup(s).