From: Michelle Konzack <linux4michelle@freenet.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Ext3 File System "Too many files" with snort
Date: Sun, 11 Jul 2004 16:55:46 +0200 [thread overview]
Message-ID: <20040711145546.GF720@freenet.de> (raw)
In-Reply-To: <20040708182143.GD23346@schnapps.adilger.int>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
Hello Andreas,
Am 2004-07-08 12:21:43, schrieb Andreas Dilger:
>If you are actually running out of inodes, then you can use "-i" or "-N"
>to mke2fs to increase the number of inodes in a new filesystem. Since
>this defaults to 1 inode per 8kB of space, it seems unlikely that you
>would run out of inodes before blocks unless you have lots of small files
>(maildir perhaps? even then "modern" emails usually average > 8kB in size
>because of HTML crap, lots of headers, attachments, etc).
I have a courier-imap Server where I share all all mailinglists where
I am subscribed... Curently I have 5,2 Millionen Messages in the ext3.
I have already striped the messages with
:0 fh
| formail -f -I Received: -I Envelope-to: -I Delivered-To: -I Return-path: \
-I X-Spam-Checker-Version: -I X-Spam-Status: -I X-Spam-Level:
I have a mailsize of around 2,5 kBytes...
So I habe used 'mkfs.ext3 -b 1024 -N 8000000 ... /dev/sda..'
My question is, how many Inodes can I create on a ext3 filesystem ?
Curently I am running a 3Ware Raid-5 Controller 75xx with 3 x 80 GByte.
>Cheers, Andreas
Greetings
Michelle
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-11 14:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 17:51 Ext3 File System "Too many files" with snort jmerkey
2004-07-08 18:21 ` Andreas Dilger
2004-07-11 14:55 ` Michelle Konzack [this message]
2004-07-11 17:16 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2004-07-09 16:36 jmerkey
2004-07-09 17:04 ` Dave Jones
2004-07-09 18:30 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:51 jmerkey
2004-07-09 19:01 jmerkey
2004-07-09 19:08 ` Pete Harlan
2004-07-14 3:37 ` Ben Hoskings
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 23:11 jmerkey
2004-07-10 6:00 jmerkey
2004-07-10 8:38 ` Dave Jones
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=20040711145546.GF720@freenet.de \
--to=linux4michelle@freenet.de \
--cc=linux-kernel@vger.kernel.org \
/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