Once native gluster clients get correct UID and GID information from the volume, the next command reports wrong UID and GID information.

Solution Verified - Updated -

Issue

  • Once native gluster clients get correct UID and GID information from the volume, the next command reports wrong UID and GID information.
    For example,

    [root@node1 test]# stat 20140305 <--- This is first time.
      File: `20140305'
      Size: 1368            Blocks: 0          IO Block: 131072 directory
    Device: 1ch/28d Inode: 9958918150385401850  Links: 2
    Access: (0755/drwxr-xr-x)  Uid: ( 2002/     test)   Gid: ( 2001/  testgrp) <--- correct GID and UID were shown.
    Access: 2014-04-24 10:31:14.000000000 +0900
    Modify: 2014-09-03 14:41:30.301084319 +0900
    Change: 2015-01-23 11:28:09.659964538 +0900
    
    [root@node1 test]# stat 20140305 <--- This is second time.
      File: `20140305'
      Size: 1368            Blocks: 0          IO Block: 131072 directory
    Device: 1ch/28d Inode: 9958918150385401850  Links: 2
    Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root) <--- UID and GID changed.
    Access: 2014-04-24 10:31:14.000000000 +0900
    Modify: 2014-09-03 14:41:30.301084319 +0900
    Change: 2015-01-23 11:28:09.659964538 +0900
    

Environment

  • Red Hat Storage Server 2.1 and 3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.