Bug 1749272 - The version of the file in the disperse volume created with different nodes is incorrect
Summary: The version of the file in the disperse volume created with different nodes i...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-05 09:28 UTC by Carlos
Modified: 2020-03-12 12:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 12:14:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Carlos 2019-09-05 09:28:08 UTC 
Description of problem:
    Hi, I built a disperse volume with 4+1 configuration between five nodes, NFS mounted this volume on a folder. Then did some I/O in this folder. I shutdown a node in the process of I/O, then I/O error happened.
    There are some xattrs in Additional Info, the version of Node 1 is different from the others. What kind of reasons would cause this result?


Version-Release number of selected component (if applicable):
    Gluster 4.1.8

Additional info:
    I fetched ec xattrs on four nodes (except the node which is shutdown), the version of Node 1 is different from the other nodes.

Node 1:
    trusted.ec.dirty=0x000000000000002b000000000000002b
    trusted.ec.version=0x0000000000005d210000000000005d23

Node 2:
    trusted.ec.dirty=0x000000000000002b000000000000002b
    trusted.ec.version=0x0000000000005d250000000000005d27

Node 3:
    trusted.ec.dirty=0x000000000000002b000000000000002b
    trusted.ec.version=0x0000000000005d250000000000005d27

Node 4:
    trusted.ec.dirty=0x000000000000002b000000000000002b
    trusted.ec.version=0x0000000000005d250000000000005d27

Node 5: (Shutdown)
Comment 1 Worker Ant 2020-03-12 12:14:51 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/849, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.