search for: bmidata1

...t indices for brick numbers. Info uses 1 based but heal statistics uses 0 based. gluster volume info clifford Volume Name: cliffordType: 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.addres...

That took a while! I have the following stats: 4085169 files in both bricks3162940 files only have a single hard link. All of the files exist on both servers. bmidata2 (below) WAS running when bmidata1 died. gluster volume 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 bmidata...

...6563745f723a756e6c616265 > > 6c65645f743a733000 > > > > > > trusted.bit-rot.version=0x020000000000000059b1b316000270e7 > > > > > > trusted.gfid=0x0000a5ef5af7401b84b5ff2a51c10421 > > > > > > > > > > > > [root at bmidata1 brick]# getfattr -d -n trusted.glusterfs.pathinfo -e > > hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 > > > > > > .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421: > > trusted.glusterfs.pathinfo: No such attribute > > > > > &gt...

...0/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 > > security.selinux=0x73797374656d5f753a6f626a6563 > 745f723a756e6c6162656c65645f743a733000 > > trusted.bit-rot.version=0x020000000000000059b1b316000270e7 > > trusted.gfid=0x0000a5ef5af7401b84b5ff2a51c10421 > > > > [root at bmidata1 brick]# getfattr -d -n trusted.glusterfs.pathinfo -e hex > -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 > > .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421: > trusted.glusterfs.pathinfo: No such attribute > > > > I had to totally rebuild the dead RAID arr...

...> # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 > security.selinux=0x73797374656d5f753a6f626a6563 > 745f723a756e6c6162656c65645f743a733000 > trusted.bit-rot.version=0x020000000000000059b1b316000270e7 > trusted.gfid=0x0000a5ef5af7401b84b5ff2a51c10421 > > [root at bmidata1 brick]# getfattr -d -n trusted.glusterfs.pathinfo -e hex > -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 > .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421: > trusted.glusterfs.pathinfo: No such attribute > > I had to totally rebuild the dead RAID array and did a co...

...000a5ef-5af7-401b-84b5-ff2a51c10421# file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5- ff2a51c10421security.selinux=0x73797374656d5f753a6f626a6563745f723a756e 6c6162656c65645f743a733000trusted.bit- rot.version=0x020000000000000059b1b316000270e7trusted.gfid=0x0000a5ef5a f7401b84b5ff2a51c10421 [root at bmidata1 brick]# getfattr -d -n trusted.glusterfs.pathinfo -e hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5- ff2a51c10421.glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421: trusted.glusterfs.pathinfo: No such attribute I had to totally rebuild the dead RAID array and did a copy from the live one befo...

...00a5ef-5af7-401b-84b5-ff2a51c10421 # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.bit-rot.version=0x020000000000000059b1b316000270e7 trusted.gfid=0x0000a5ef5af7401b84b5ff2a51c10421 [root at bmidata1<mailto:root at bmidata1> brick]# getfattr -d -n trusted.glusterfs.pathinfo -e hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421: trusted.glusterfs.pathinfo: No such attribute I had to totally rebuild the dead RAID array and d...

...ted.bit-rot.version=0x020000000000000059b1b316000270e7 > > > > > > > > > > > > trusted.gfid=0x0000a5ef5af7401b84b5ff2a51c10421 > > > > > > > > > > > > > > > > > > > > > > > > [root at bmidata1 brick]# getfattr -d -n > > > > trusted.glusterfs.pathinfo -e hex -m . > > > > .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421 > > > > > > > > > > > > .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421: > > > > truste...

Attached is the heal log for the volume as well as the shd log. >> Run these commands on all the bricks of the replica pair to get the attrs set on the backend. [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 getfattr: Removing leading '/' from absolute path names # file:

Hi Matt, Run these commands on all the bricks of the replica pair to get the attrs set on the backend. On the bricks of first replica set: getfattr -d -e hex -m . <brick path>/.glusterfs/10/86/ 108694db-c039-4b7c-bd3d-ad6a15d811a2 On the fourth replica set: getfattr -d -e hex -m . <brick path>/.glusterfs/ e0/c5/e0c56bf7-8bfe-46ca-bde1-e46b92d33df3 Also run the "gluster volume