Re: Ext3 File System "Too many files" with snort

[jmerkey]

> >NetWare has always supported more than this, so this whole idea of fixed inode 
> tables 
> >is somewhat strange to me to start with.  I am still looking through Hans code, 
> but if 
> >this is accurate I'll just take a system out Monday and see if it works.  My 
> only concern 
> >with Reiser has to do with the bug reports I've seen on it over the years, but 
> Suse is 
> >shipping it as default, and we have been running it here for about a year on a 
> production 
> >server.  I'll post if it crashes, corrupts data, or has problems.  
> >
> >Jeff
> >
> >
> Don't use it on redhat systems, those bug reports tend to be for redhat 
> kernels, redhat refuses to apply our bugfixes that we send in to the 
> official kernel because they want us to look bad.  I sound so paranoid 
> when I say that, but they really do refuse to apply our bugfixes.

Not nice at all to not post updates.  They don't respond to email much either.   

> 
> ReiserFS V3 has been very stable for quite some time in 2.4.x.  There 
> were some instabilities recently in some versions of 2.6.x due to code 
> changes not by our team. sigh....
> 
> We at Namesys are much more conservative in code changes for V3 than 
> ext*.  I can't control some of the changes by SuSE though that have 
> added some bugs that could have been caught by more serious QA.  (SuSE 
> adheres to the usual linux lack of QA approach, it is not that they are 
> bad, but that they conform to the social norm for linux.)  Hopefully I 
> will have more control over that in V4.

We are using Suse for appliance builds for customer shipments.  More stable, 
more features, better quality.  I will be using Suse for the site with Reiser 
Monday.  So far looks good.  Builds finished tonight on 2.6 and running stable.

I will post a report of any problems at the site with Reiser.  From initial tests, looks
fixed.

:-)

> 
> Hans

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/