I took one of the gfids and found the actual path to the file on the brick. I then did: getfattr -d -m . -e hex <ACTUAL_PATH> security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.afr.<VOLNAME>-client-6=0x000000020000000100000000 trusted.afr.dirty=0x000000000000000000000000 trusted.bit-rot.version=0x02000000000000005a7e0cdb000196c6 trusted.gfid=0xa65bac27fd504c899ba4457675ed5518 trusted.pgfid.eb6d6fa2-339e-4dd7-a642-ca755d5f47cf=0x00000001 Which must mean that client-6 had a problem with both the data and metadata. I then went to client-6 and issued the same getfattr command: getfattr -d -m . -e hex <ACTUAL_PATH> security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.afr.dirty=0x000000000000000000000000 trusted.bit-rot.version=0x02000000000000005a7e0cdb00018323 trusted.gfid=0x06df01f614fa40fda3b628265ba36318 trusted.pgfid.eb6d6fa2-339e-4dd7-a642-ca755d5f47cf=0x00000001 As you can see, the gfid is different between the clients for the same file path. Doing a file operation on this file via the mount results in Input/Output error. Doing a stat on the parent directory doesn’t do anything either. What’s a good way to mover forward from here? Unrelated: what’s dht.linkto attribute used for? Thanks! Sergei
|
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users