Hi Larry,
Can you share with us the volume files you are using with GlusterFS?.
Also the scripts you are trying to run.
Thanks
--
Harshavardhana
Gluster - http://www.gluster.com
On Tue, Jan 26, 2010 at 3:31 AM, Larry Bates <larry.bates at vitalesafe.com>wrote:
> Well it seems that I can register, but the registration of the subfolders
> is so
> slow that I thought it was not working. I have subfolders 00-ff and
> subfolders
> under them 00-ff (64K total folder structure). Registering on normal
> storage
> took about 30 seconds. Registering inotify watcher (recursive=True) on
> GlusterFS mount takes over 1 hr, 15 min! Walking the tree and registering
> them
> each individually takes 6 minutes.
>
> -Larry
>
> -----Original Message-----
> From: Larry Bates [mailto:larry.bates at vitalesafe.com]
> Sent: Monday, January 25, 2010 1:51 PM
> To: 'gluster-users at gluster.org'
> Subject: GlusterFS and inotify
>
> I recently moved my backend storage to GlusterFS V3.0 and with one
> exception
> everything is running great. That exception is that I had a daemon using
> inotify that was watching my storage for new files. Upon arrival this
> watcher
> uploaded a copy of the file to Amazon S3. This daemon had been running
> just
> fine for well over a year. Moving to GlusterFS seems to indicate that
> inotify
> doesn't work on GlusterFS volumes. I don't know if it is a Gluster, Fuse,
> or
> some other problem. inotify just refuses to allow me to register the top
> level
> folder to be watched. Before I spend a lot of time on this, I thought I'd
> bounce it off of the "experts" on this list.
>
> Anyone have any ideas?
>
> Thanks in advance,
> Larry Bates
> vitalEsafe, Inc.
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
