On 27 Jan 2003, Roach, Mark R. wrote:
> Hi, all. I am running up against some strange fam problems in my
> attempts to mirror a couple of linux file servers.
>
> I have a directory with 2089 subdirectories and 37239 files in those
> subdirectories. I am using the python-fam bindings from
> python-fam.sf.net.
>
> My first problem came when queuing too many directories without reading
> in the events - my process kept hanging, I made two separate threads to
> send/recv at the same time and that part seems ok, but once I have the
> monitor set, if I create a file, fam doesn't recognize that the file was
> created and tells me that all other files in that directory were
> deleted.
It typically hangs because the pipes for recieving events are full, so
the fam server refuses to read more requests from the client (to avoid
blocking on write). Making sure you read events would help with this, so
the multithreaded solution would help. I'm not 100% sure libfam is
threadsafe though...
> This is obviously not the desired result, any clues as to how I can
> prevent this kind of stuff? Am I going to need to break this down into
> multiple processes with fewer directories handled by each process? Is
> this just too much for fam to handle?
The deleted message is quite strange. I have no idea why that's happening.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl@xxxxxxxxxx alla@xxxxxxxxxxxxxx
He's an obese guerilla shaman plagued by the memory of his family's brutal
murder. She's a psychotic cat-loving archaeologist with the power to see
death. They fight crime!
|