From: "Sean Elble" <S_Elble@yahoo.com>
To: "Mike Fedyk" <mfedyk@matchmail.com>, "Brian" <hiryuu@envisiongames.net>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: File server FS?
Date: Tue, 13 Nov 2001 21:05:49 -0500 [thread overview]
Message-ID: <028201c16cb0$f489ccc0$0a00a8c0@intranet.mp3s.com> (raw)
In-Reply-To: <200111132203.fADM3jW03006@demai05.mw.mediaone.net> <20011113175348.B24864@mikef-linux.matchmail.com>
I'd have to recommend XFS for you . . . it supports the kernel mode NFS
server very well, it supports LVM, an XFS file system can be enlarged (not
reduced), and XFS has great quota support, just be sure you use a 3.0 or
greater quota tools package. Why use XFS over Ext3 you ask? XFS is faster,
and scales better, IMHO. Again just my opinion, but I hope that helps.
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
elbles@reactivelinux.com
-----------------------------------------------
----- Original Message -----
From: "Mike Fedyk" <mfedyk@matchmail.com>
To: "Brian" <hiryuu@envisiongames.net>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 13, 2001 8:53 PM
Subject: Re: File server FS?
> On Tue, Nov 13, 2001 at 05:03:34PM -0500, Brian wrote:
> > We are about to build a fairly large (720GB) file server using Linux.
No
> > sane person would actually want to watch this thing fsck, but I've seen
> > mixed reports about the functionality of the journaled FSes.
> >
>
> Ext3!
>
> > Specifically, I need support for
> > * KNFSD - it is a file server, afterall
>
> Yep
>
> > * LVM - For snapshots and to add space later
>
> Yep
>
> > * Resizing - See last point
>
> There are two utilities to resize ext2, which ext3 is except for an
> additional file (journal) after umount.
>
> > * Quotas - Eventually, but we don't need it just yet
> >
>
> A little tricky in Linus' kernel. Should be sorted out soon.
>
> > Which, if any, of the journaled FSes support these?
> > Which one should I go with for a wide range of file and directory sizes?
> >
>
> How many files in a single dir? Reiser is great for that, but not so good
> for fragmentation after time on a 70% full or more FS...
>
> There is indexing in development for ext2/3, but that'll be 2.5 work.
>
> Mike
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-11-14 2:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 22:03 File server FS? Brian
2001-11-14 1:53 ` Mike Fedyk
2001-11-14 2:05 ` Sean Elble [this message]
2001-11-14 10:41 ` Robert Szentmihalyi
2001-11-14 15:10 ` Steve Lord
2001-11-14 16:09 ` Robert Szentmihalyi
2001-11-17 18:12 ` Jamie Lokier
2001-11-17 21:55 ` Mike Fedyk
2001-11-17 22:10 ` Andrew Morton
2001-11-17 22:23 ` Mike Fedyk
2001-11-17 22:31 ` Andrew Morton
2001-11-17 22:38 ` Andreas Dilger
2001-11-18 1:34 ` Jamie Lokier
2001-11-17 22:27 ` Andreas Dilger
2001-11-16 10:19 ` Pavel Machek
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='028201c16cb0$f489ccc0$0a00a8c0@intranet.mp3s.com' \
--to=s_elble@yahoo.com \
--cc=hiryuu@envisiongames.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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