[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] doing fsync after fetching news



Andrey Ulanov <drey@xxxxxxxxxx> writes:

> I use leafnode with reiserfs. The problem appears when i reboot the
> system without syncing disks. Does leafnode do fsync for ever
> fetched message? It seems it does not.

Welcome to the world of meta data journalling file systems. They recover
the file names for you, but not the file contents after a crash. There's
nothing leafnode could fix.

fsync() for articles fetched from the upstream would slow down fetching
even more.

> So after reboot there is garbage in messages. And when i try to read
> corrupter messages it writes to logs:
>
> Jan  9 10:24:55 vocord leafnode[24696]: <d (no trailing LF)
>
> And client hangs up waiting for the reply from server. And to fix the
> problem i need to remove corrupted messages by hands.

Oh hum, there might be another leafnode bug, or it might be a client
bug. Can you send me one of the broken article files to my private
address?

OTOH, texpire should also kill corrupted articles.

-- 
Matthias Andree
leafnode-1 download: http://sourceforge.net/projects/leafnode/
leafnode-1 docs/new: http://mandree.home.pages.de/leafnode/
leafnode-2 homepage: http://mandree.home.pages.de/leafnode/beta/

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list