From: harlan@artselect.com (Pete Harlan)
To: jmerkey@comcast.net
Cc: Hans Reiser <reiser@namesys.com>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org
Subject: Re: Ext3 File System "Too many files" with snort
Date: Fri, 9 Jul 2004 14:08:23 -0500 [thread overview]
Message-ID: <20040709190823.GC11106@artselect.com> (raw)
In-Reply-To: <070920041901.1676.40EEEB880003599F0000068C2200763704970A059D0A0306@comcast.net>
Reiser3 lets a directory have more than 32000 subdirectories already.
I ran into this problem two weeks ago on an ext3 filesystem and found
Reiser didn't have the problem. My reiser3 directory had 1million+
subdirs before I killed my test program.
I believe it still has a similar limit on the number of hard links,
but it doesn't implement ".." as a hard link.
--Pete
On Fri, Jul 09, 2004 at 07:01:28PM +0000, jmerkey@comcast.net wrote:
>
> Hans,
>
> I forgot to mention I am running on Suse 9.1 with 2.6.4 but can upgrade this software
> to 2.6.whatever. If you could hand me a patch or some instructions as to which files
> to modify, I'll attempt to make these changes and test them. Reiser seems a little more
> complex than most of the other FS's and I am somewhat hesitant to alter it and place
> it into a production system based on a lot of bug reports I;ve seen over the years. It's
> very powerful, but also very complex and I probably **WILL** break something if I
> attempt to change your code. Can you point me to where the changes and/or send
> me a simple patch to remove the 32000 directory limitation and increase support to 32
> bit the the nlink field?
>
> Danke,
>
> Jeff
>
>
> > >
> > Just use reiser4 which has disk format plugins. reiserfs v3 should stay
> > stable and undisturbed.
> >
>
> I was actually looking through your code when this message arrived. I am
> sending out
> another unit Monday to the site installed with reiser and Suse Linux, Might I
> suggest
> perhaps you consider making the change in reiser for the larger field size to 32
> bit (I
> am looking at the code at present, and it appears you are using the same inode
> structure as everyone else) and I will default these systems to reiser instead
> of EXT3
> for this application. There's another FS (not NWFS) that actually writes the
> captured
> network traffic streaming to the system at over 400 MB/S which folks haven't
> seen
> yet, it acts more like on on-disk LRU with huge cache units (137 MB each)
> but snort and the network forensic applications use a standard file system for
> reporting. Reiser is a good choice if this limitation can be removed.
>
> Veil Erfolg and Gluck.
>
> Danke,
>
> Jeff
>
> Bitte
>
>
>
> > >Jeff
> > >
> > >
> > >>-Andi
> > >>
> > >>
> > >>
> > >-
> > >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/
> > >
> > >
> > >
> > >
> >
> -
> 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:[~2004-07-09 19:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 19:01 Ext3 File System "Too many files" with snort jmerkey
2004-07-09 19:08 ` Pete Harlan [this message]
2004-07-14 3:37 ` Ben Hoskings
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 6:00 jmerkey
2004-07-10 8:38 ` Dave Jones
2004-07-09 23:11 jmerkey
2004-07-09 19:20 jmerkey
2004-07-10 5:07 ` Hans Reiser
2004-07-10 8:33 ` Dave Jones
2004-07-10 17:37 ` Hans Reiser
2004-07-10 17:44 ` Christoph Hellwig
2004-07-10 17:57 ` Hans Reiser
2004-07-10 18:54 ` Christoph Hellwig
2004-07-10 19:23 ` Hans Reiser
2004-07-12 10:20 ` Paolo Ciarrocchi
2004-07-12 12:11 ` Jesper Juhl
2004-07-12 23:05 ` Bernd Eckenfels
2004-07-18 7:22 ` Hans Reiser
2004-07-10 19:11 ` Francois Romieu
2004-07-09 18:51 jmerkey
2004-07-09 18:30 jmerkey
2004-07-09 18:44 ` Hans Reiser
2004-07-09 22:26 ` Andreas Dilger
2004-07-09 18:30 jmerkey
2004-07-09 16:36 jmerkey
2004-07-09 17:04 ` Dave Jones
2004-07-08 17:51 jmerkey
2004-07-08 18:21 ` Andreas Dilger
2004-07-11 14:55 ` Michelle Konzack
2004-07-11 17:16 ` Andreas Dilger
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=20040709190823.GC11106@artselect.com \
--to=harlan@artselect.com \
--cc=ak@muc.de \
--cc=jmerkey@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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 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.