After the upgrade, one of my four storage servers was successfully running glusterd, but no glusterfsd processes were present for bricks on that server. I believe this had to do with the fact that this was the first server I created under 3.1.1, and that I had somehow misconfigured peers for it, since it showed no peers. I also an entry for this server and one other storage server in /etc/hosts, which I removed. Once these issues were resolved, restarting the glusterd process worked fine and the bricks were visible. The client problem was that, after doing the above to the storage servers, the client(s) obviously had cache issues. Doing an "ls" on a native GlusterFS mount showed only several subdirectories out of many, and a "du -sh" of the mount point gave this message on the client: du: fts_read failed: No such file or directory Clearing the client cache as suggested did not resolve this problem, but restarting the client (I have my own /etc/init.d/gluster-client script, which basically loads and unloads the gluster-fuse module and does the mounts and dismounts) cleared up the problem. James Burnash Unix Engineer Knight Capital Group From: Harshavardhana [mailto:harsha at gluster.com] Sent: Wednesday, June 22, 2011 3:11 PM To: Burnash, James Cc: John Mark Walker; gluster-users at gluster.org Subject: Re: GlusterFS 3.1.5 now available That was to clear page-cache on the client side, usually some of the issues related to cache-coherency with stat-prefetch, quick-read and io-cache get resolved temporarily. In general this is not a good practice since the application has to invalidate it caches proactively and keep track of them as necessary. James, i need to know the reason behind doing it. Was it just a hunch or is there any specific errors you are seeing after the upgrade? On Wed, Jun 22, 2011 at 12:05 PM, Burnash, James <jburnash at knight.com<mailto:jburnash at knight.com>> wrote: I'll add it :) James Burnash Unix Engineer Knight Capital Group From: John Mark Walker [mailto:jwalker at gluster.com<mailto:jwalker at gluster.com>] Sent: Wednesday, June 22, 2011 3:04 PM To: Harshavardhana; Burnash, James Cc: gluster-users at gluster.org<mailto:gluster-users at gluster.org> Subject: RE: GlusterFS 3.1.5 now available This looks like the type of Q &A which should go on http://community.gluster.org/ :) I'll add it if nobody else does. -JM ________________________________ From: gluster-users-bounces at gluster.org<mailto:gluster-users-bounces at gluster.org> [gluster-users-bounces at gluster.org<mailto:gluster-users-bounces at gluster.org>] on behalf of Harshavardhana [harsha at gluster.com<mailto:harsha at gluster.com>] Sent: Wednesday, June 22, 2011 11:56 AM To: Burnash, James Cc: gluster-users at gluster.org<mailto:gluster-users at gluster.org> Subject: Re: GlusterFS 3.1.5 now available On Wed, Jun 22, 2011 at 11:53 AM, Burnash, James <jburnash at knight.com<mailto:jburnash at knight.com>> wrote: Does anyone know how we can get the native GlusterFS clients to clear their cached data short of restarting them (or dismounting and remounting their gluster storage? Clients are running 3.1.3, servers are now running 3.1.5. Client side 'caches' are in page cache to invalidate those all you have to do is echo '3' > /proc/sys/vm/drop_caches Regards -- Harsha Gluster Inc DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the addressee(s)named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com<http://www.knight.com/> -- Harsha Gluster Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20110622/ee37d6b9/attachment.htm>