Description of problem: ======================= When a brick is brought down following message is logged every 3 sec in glusterd logs: [2014-06-27 10:28:12.693185] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:15.694036] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:18.694114] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:21.694459] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:24.694963] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:27.695196] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:30.696703] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:33.696101] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:36.696439] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) [2014-06-27 10:28:39.697021] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) If a brick is down for weeks, then chances are there that these logs will filled the root space and make the system unusable Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.6.0.22-1.el6rhs.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: ==================== 1. Create 4 node cluster system 2. Create a volume vol0 (2*2) from 4 node cluster 3. Create a snapshot of a volume 4. Create another volume vol4 (2*3) from 3 nodes of a cluster. 5. Bring down one of the brick from vol4 (I brought down brick participating in the third node) Actual results: =============== [2014-06-27 10:28:39.697021] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/a30ad20ae7386a2fe58445b1a2b1359c.socket failed (Invalid argument) Frequency of logs is every 3sec, which has a risk to crash the complete system. The logs/failure needs investigation.
*** Bug 1121193 has been marked as a duplicate of this bug. ***
Marking this as this is a customer issue and occurring because of excessive logging.
The fix is now available in rhgs-3.1.3 branch, hence moving the state to Modified.
Verified this bug using the build "glusterfs-3.7.9-1" Brought down one of the brick in the volume and observed the glusterd log for the rate of readv warning messages The readv warning message rate is got reduced, currently warning message is populating in the glusterd log for every 2 Mins and 6 seconds ><<<<<<<<<<< [2016-04-05 04:24:27.921343] W [socket.c:589:__socket_rwv] 0-management: readv on /var/run/gluster/88f23c9fa290ee8044a4fea42da5ef1a.socket failed (Invalid argument) [2016-04-05 04:26:33.953341] W [socket.c:589:__socket_rwv] 0-management: readv on /var/run/gluster/88f23c9fa290ee8044a4fea42da5ef1a.socket failed (Invalid argument) [2016-04-05 04:28:39.990809] W [socket.c:589:__socket_rwv] 0-management: readv on /var/run/gluster/88f23c9fa290ee8044a4fea42da5ef1a.socket failed (Invalid argument) ><<<<<<<<<<< with above details, moving bug to verified state.
LGTM :)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1240