<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div>Hi,<br></div><div><br></div><div>Slow "ls -l" command which is also the reason behind TAB and df -h issue.<br></div><div>I would suggest to check "disperse.other-eager-lock" option and see if it is "ON" or "OFF"<br></div><div><br></div><div>gluster v get <volname> all | grep other</div><div><br></div><div>If it is ON, change it to OFF by following command<br></div><div>gluster v set <volname> disperse.other-eager-lock off</div><div><br></div><div>It should solve the problem.<br></div><div><br></div><div>---<br></div><div>Ashish<br></div><div><br></div><div><br></div><div><br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Mauro Tridici" <mauro.tridici@cmcc.it><br><b>To: </b>"gluster-users" <gluster-users@gluster.org><br><b>Sent: </b>Wednesday, October 24, 2018 8:20:48 PM<br><b>Subject: </b>[Gluster-users] Gluster 3.12.14: slow ls -l command + "Another transaction is in progress. Please try again after sometime" message<br><div><br></div>Dear All,<div class=""><br class=""></div><div class="">during last two days, our distributed dispersed gluster volume is showing some strange behaviors:</div><div class=""><br class=""></div><div class="">1) "df -h" and "ls -l" linux commands are very slow</div><div class="">2) “TAB” key usage causes the hang of the shell</div><div class="">3) nagios monitoring system is showing some alerts related to QUOTA and VOLUME UTILIZATION similar to the following one:</div><div class=""><br class=""></div><div class=""><i style="font-size: 14px;" class="" data-mce-style="font-size: 14px;">Notification Type: PROBLEM<br class=""><br class="">Service: Volume Quota - tier2<br class="">Host: tier2-gluster<br class="">Address: tier2-gluster<br class="">State: WARNING<br class=""><br class="">Date/Time: Wed Oct 24 16:27:13 CEST 2018<br class=""><br class="">Additional Info:<br class=""><br class="">QUOTA: Quota status could not be determined.</i></div><div class=""><br class=""></div><div class="">4) on some gluster servers, “df -h” command shows a new mount “/run/gluster/tier2_quota_list”</div><div class="">5) gluster vol status returns this message: “Another transaction is in progress. Please try again after sometime”.</div><div class=""><br class=""></div><div class="">I just restarted the “glusterd” service on each server, one by one.</div><div class="">Also, I executed “umount -l /run/gluster/tier2_quota_list” on each server.</div><div class="">Now, everything seems to be ok, but I would like to know if there is a way to avoid this kind of problem.</div><div class=""><br class=""></div><div class="">Last question: do you think that it is a good practice executing “service glusterd restart” command on each server when the problem appears? </div><div class="">In attachment you can find the glusterd.log file</div><div class=""><br class=""></div><div class="">Thank you in advance,</div><div class="">Mauro</div><div class=""><br class=""></div><div class=""><br></div><br><div class=""><br></div><div class=""><br class=""></div><div class=""><br class=""></div><br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>https://lists.gluster.org/mailman/listinfo/gluster-users</div><div><br></div></div></body></html>