On 6/9/2015 8:30 AM, Pablo Silva wrote:
Here is your problem. You are not mounting m2mas2. /opt/mendelson/messages is NOT the same as m2mas2. You can NEVER write (or read) to /opt/mendelson/messages. You must pretend that is does not exist. You must mount the Gluster volume, and use only the path to the gluster volume, never to the brick. When you write to the brick you are "going behind gluster's back" and gluster does not know that anything has changed, so it does not make those files available to the gluster clients. It may eventually notice them, and make them available, but it is not anything dependable or predictable. First, make sure you have the glusterfs-fuse package installed. You need to add a line to /etc/fstab that is like: mendelson:/m2mas2 /opt/m2m.as2 glusterfs defaults 0 0
Then change everything that you are now reading and writing to /opt/mendelson/messages so that it writes to /opt/m2m.as2 (or whatever mount point you have chosen). Many of us follow this pattern. All bricks are located at /bricks/xxx/xxx. All gluster files systems are mounted to /gluster/xxx. That makes the separation between the bricks and the gluster volumes very clear, and very hard to mess up when writing file paths in programs. No trying to remember "Which is the brick, and which is the gluster volume?" On your Apache system, you again need to mount the glusterfs volume in a separate place, and make sure that the glusterfs location is the only one that Apache knows about or uses in any way whatsoever. Ted Miller
--
Ted Miller, Design Engineer SonSet Solutions (formerly HCJB Global Technology Center) my desk +1 574.970.4272 receptionist +1 574.972.4252 http://sonsetsolutions.org Technology for abundant life! |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users