From: Philippe Troin <phil@fifi.org>
To: Greg Boehnlein <damin@nacs.net>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: Journaling FileSystems w/ NFS
Date: 21 Sep 2002 12:14:52 -0700 [thread overview]
Message-ID: <87lm5vupcj.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0209201322050.25485-100000@node1.nacs.net>
Greg Boehnlein <damin@nacs.net> writes:
> Let me bring you up to speed on what we are doing, and provide an accurate
> idea of what our needs and requirements are. Instead of backing our data
> up directly to tape, we instead dump it to a large 320 Gig, RAID-5
> partition on a Linux box. That, in turn, is backed up to tape on a regular
> basis and taken offsite. Recent growth of data on some of our "Cobalt Raq"
> servers has forced us to upgrade to a filesystem that can handle file
> sizes of greater than 2 gigs. (Why Cobalt doesn't split their backup
> archives into multiple pieces is beyond me). On occasion, this partition
> needs to be accessible via NFS for other Servers and workstations.
> Obviously with a file system of that size, a journaling system would be
> advantageous.
>
> So, we need three main things:
> 1. Journaling File System
> 2. Large file support
> 3. NFS Compatibility
>
> I had suggested XFS to my Operations Manager, but he decided to try using
> JFS, as it was an included option in RedHat 7.3. Installation went
> beautifully, and everything was peachy, until we tried to export that
> file-system via NFS. Doing so caused the load average on the box to
> skyrocket.. Apparently, NFS and JFS don't get along very well together.
>
> Our solution? Use XFS. ;) However, there do appear to be issues between
> JFS and NFS... Not sure where, or what, but I thought I'd mention it.
I'd be curious to know why you did not choose the "easy" solution:
ext3. It is journalled, it has LFS support, and works flawlessly with
NFS.
Phil.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-09-21 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 15:48 Journaling FileSystems w/ NFS Greg Boehnlein
2002-09-20 16:26 ` Magnus Naeslund(f)
2002-09-20 16:56 ` Magnus Naeslund(f)
2002-09-21 11:36 ` Greg Boehnlein
2002-09-21 12:13 ` Chris Tooley
2002-09-21 19:14 ` Philippe Troin [this message]
2002-09-21 21:58 ` Greg Boehnlein
2002-09-22 1:08 ` Philippe Troin
2002-09-20 16:40 ` seth vidal
2002-09-20 17:17 ` Juergen Sauer
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 21:30 pwitting
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=87lm5vupcj.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=damin@nacs.net \
--cc=nfs@lists.sourceforge.net \
/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.