Bug 802025 - User complaining of memory errors during geo-rep
Summary: User complaining of memory errors during geo-rep
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.2.5
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Venky Shankar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-10 10:33 UTC by Joe Julian
Modified: 2013-01-11 05:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-11 05:11:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Joe Julian 2012-03-10 10:33:29 UTC
An IRC user was complaining of "OSError: [Errno 12] Cannot allocate memory" error messages. I tracked them down to a Server::xtime buffer overflow. In resource.py:144
  return struct.unpack('!II', Xattr.lgetxattr(path, '.'.join([cls.GX_NSPACE, uuid, 'xtime']), 8))

Apparently getattr is overflowing the fixed "8". The user stopped responding after I found that problem so I have no further diagnostic details.

Comment 1 Venky Shankar 2013-01-11 05:11:15 UTC
I could not reproduce this in my setup. Also the bug does not have enough information (geo-rep [mount] log files, backtraces) to make some assumptions/about the error.

I'm closing this with "INSUFFICIENT DATA" for now. Please reopen if someone hits this again.


Note You need to log in before you can comment on or make changes to this bug.