INN-base feeder

["Miquel van Smoorenburg"]

In article <20030125214223.GC2617 at virgin.gazeta.pl>,
Przemys³aw Maciuszko  <sal at agora.pl> wrote:
>On Sat, Jan 25, 2003 at 12:33:07PM +0000, "Miquel van Smoorenburg"  wrote:
>> Don't put history on ext3, that might slow it down a lot due to the
>> journal. Put it on ext2.
>> Did you put the CNFS buffers on an ext3 filesystem as well? That will
>> hurt, I think.
>
>Yes. Both of those hurt :( Thath's why I'm thinking of moving it to
>_anything_ else. That's why I ask "move it to what?"

Ext2 would be fine for the history database. If the server crashes,
the filesystem will be clean with ext3, but the history (and overview)
databases will be corrupt anyway. So for data integrety it really
doesn't matter if you use ext2 or ext3. Ideally ext3 would have
an API to the transaction stuff and INN would know how to use
it with the history and overview databases, but I don't see that
happening in the next few years.

>> Don't put the CNFS buffers on a filesystem. Use a 2.4.20 kernel,
>> compile INN with largefile-support, and use partitions as CNFS buffers-
>> and preferably, don't use more than one CNFS buffer per disk to
>> prevent seeking.
>
>Ok. So all I have to do is move CNFS buffers to raw-devices.

And history to an ext2 partition. You can just mount the partition
as ext2 instead of ext3, that will work fine. Ext2 and ext3 are
interchangeable (as long as the filesystem was unmounted cleanly)

I'd probably try that first, since you can do it in a matter
of minutes.

Mike.
-- 
Anyone who is capable of getting themselves made President should
on no account be allowed to do the job -- Douglas Adams.

-- 
The From: and Reply-To: addresses are internal news2mail gateway addresses.
Reply to the list or to "Miquel van Smoorenburg" <miquels at cistron.nl>