Ugh, reiserfs is a journalling filesystem and should have no problems with files larger than 2 GB.
To be on the safe side you could however check here for all things reiserfs (got the URL from the manpage of mkreiserfs) http://www.namesys.com/ We also happen to have a SEL9 box running. There I checked what the stock SuSE kernel got compiled with (n.b. most distributors place their kernel's config file in the /boot dir) # uname -r 2.6.5-7.191-pseries64 # grep -i reiser /boot/config-$(uname -r) CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set CONFIG_REISERFS_PROC_INFO=y CONFIG_REISERFS_FS_XATTR=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_REISERFS_FS_SECURITY=y Looks only REISERFS_CHECK isn't enabled. # rpm -qa|grep -i reiser reiserfs-3.6.19-3.2 # rpm -ql reiserfs /sbin/debugreiserfs /sbin/fsck.reiserfs /sbin/mkfs.reiserfs /sbin/mkreiserfs /sbin/reiserfsck /sbin/reiserfstune /sbin/resize_reiserfs /usr/share/man/man8/debugreiserfs.8.gz /usr/share/man/man8/fsck.reiserfs.8.gz /usr/share/man/man8/mkfs.reiserfs.8.gz /usr/share/man/man8/mkreiserfs.8.gz /usr/share/man/man8/reiserfsck.8.gz /usr/share/man/man8/reiserfstune.8.gz /usr/share/man/man8/resize_reiserfs.8.gz I guess your Reiserfs support looks pretty similar. I checked the mount options for Reiserfs but couldn't find any hint at all relating to large files. Anyway, this isn't getting you any further, and I guess it must then be another Tomcat imposed restriction. I can remember that I ran into troubles when I built Net-SNMP from the sources on hpux with the ANSI C HP compiler until I realized that the application was only 32bit capable. I know that Java once emerged with the posture to erradicate any type mismatches but who can tell what kind of mappings JVMs on different platform behind the scenes. Nevertheless, I wouldn't let my logfiles grow that large. As I said, no standard editor or pager is handling such beasts satisfactorily. Since you are running Linux anyway you also should have logrotate on board. Run "rpm -qi logrotate" to check. logrotate is very easy to set up. Once added a stanza for your tomcat logs you should never ever worry about files becoming too large or filesystems getting full. Just see "man logrotate", there are examples in it. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 02, 2006 12:20 PM > To: Tomcat Users List > Subject: RE: Catalina.out gets to big-> Server crashes > > > Hello Ralph, > > well it's SUSE ES 9. The filesystem is Reiserfs. The system was set up > recently. The server got multiple processors. But I can't > tell you more > cause I don't have access to it again until monday. > > cheers, > Pete > > > --- Ursprüngliche Nachricht --- > > Von: <[EMAIL PROTECTED]> > > An: <users@tomcat.apache.org> > > Betreff: RE: Catalina.out gets to big-> Server crashes > > Datum: Thu, 2 Feb 2006 11:55:39 +0100 > > > > Good Morning Pete, > > > > although I have no Tomcat knowledge whatsoever > > (only subscribed to the list in order to learn more and seek for > > an answer to my trivia questions) > > the fact that your Tomcat crashes when a logfile reached the 2 GB > > boundary > > in my opinion has nothing to do with Tomcat but rather the > > underlying filesystem Tomcat is logging to. > > Usually old type filesystems could only write 2^31 bytes unless > > the filesystem provided a so > > called largefile extension. > > Modern journaling filesystems have far higher limits for single > > file sizes. > > What type of filesystem do you use? > > Besides, I'd strongly advise to employ logrotate on your > > logfiles. > > No admin can comfortably handle logfiles that big. > > Any log rotation mechanism would automatically rotate the files > > either on a set time interval > > or if a set size is reached. > > > > HTH > > Ralph > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, February 02, 2006 11:09 AM > > > To: Tomcat Users List > > > Subject: Catalina.out gets to big-> Server crashes > > > > > > > > > Hello, > > > > > > I got this problem that the catalina.out file gets to big. It > > grows to > > > a size of approx. 2 gig and then tomcat just crashes. > > > > > > Does anyone know how configure tomcat so that catalina.out > > > only get a size > > > of 100 MB and then replaces it by a new empty catalina.out? > > > The old one > > > should be saved under a different name. > > > > > > cheers, > > > Pete > > > > > > -- > > > Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne > > Risiko! > > > Satte Provisionen fur GMX Partner: > > http://www.gmx.net/de/go/partner > > > > > > > > ----------------------------------------------------------------- > > ---- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > ----------------------------------------------------------------- ---- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > Telefonieren Sie schon oder sparen Sie noch? > NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie > > ----------------------------------------------------------------- ---- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
