search for: clifford3

...dType: Distributed- ReplicateVolume ID: 0e33ff98-53e8-40cf-bdb0-3e18406a945aStatus: StartedSnapshot Count: 0Number of Bricks: 2 x 2 = 4Transport-type: tcpBricks:Brick1: bmidata1:/data/glusterfs/clifford/brick/brickBrick2: bmidata2:/data/glusterfs/clifford/brick/brickBrick3: bmidata1:/data/glusterfs/clifford3/brick/brickBrick4: bmidata2:/data/glusterfs/clifford3/brick/brickOptions Reconfigured:cluster.self-heal-readdir-size: 4KBdisperse.background- heals: 16transport.address-family: inetperformance.readdir-ahead: oncluster.background-self-heal-count: 20cluster.self-heal-window-size: 16cluster.self-heal-...

...ume heal clifford statistics heal-countGathering count of entries to be healed on volume clifford has been successful Brick bmidata1:/data/glusterfs/clifford/brick/brickNumber of entries: 0 Brick bmidata2:/data/glusterfs/clifford/brick/brickNumber of entries: 296252 Brick bmidata1:/data/glusterfs/clifford3/brick/brickNumber of entries: 1 Brick bmidata2:/data/glusterfs/clifford3/brick/brickNumber of entries: 182407 Why those numbers are so much smaller than the data from a stat run through the entire brick, I have no idea. The 20TB of space for this mount point is composed of 4 10TB brick in a 2x2. As...

I'm not so lucky. ALL of mine show 2 links and none have the attr data that supplies the path to the original. I have the inode from stat. Looking now to dig out the path/filename from xfs_db on the specific inodes individually. Is the hash of the filename or <path>/filename and if so relative to where? /, <path from top of brick>, ? On Mon, 2017-10-23 at 18:54 +0000, Matt Waymack

Hi Jim, Can you check whether the same hardlinks are present on both the bricks & both of them have the link count 2? If the link count is 2 then "find <brickpath> -samefile <brickpath/.glusterfs/<first two bits of gfid>/<next 2 bits of gfid>/<full gfid>" should give you the file path. Regards, Karthik On Tue, Oct 24, 2017 at 3:28 AM, Jim Kinney