No-one has any suggestions? To recap: I try to delete a file, and get this: [root@g-unit-1 ~]# rm /gluster/vol00/data/CentOS3/CentOS_6.4_Final/EFI/BOOT/BOOTX64.efi rm: remove regular file `/gluster/vol00/data/CentOS3/CentOS_6.4_Final/EFI/BOOT/BOOTX64.efi'? y rm: cannot remove `/gluster/vol00/data/CentOS3/CentOS_6.4_Final/EFI/BOOT/BOOTX64.efi': No such file or directory Even when the file is clearly tagged with gluster info, so gluster knows about it: [root@g-unit-2 ~]# getfattr -m . -d -e hex /mnt/glusterfs/bricks/2/data/CentOS3/CentOS_6.4_Final/EFI/BOOT/BOOTX64.e fi getfattr: Removing leading '/' from absolute path names # file: mnt/glusterfs/bricks/2/data/CentOS3/CentOS_6.4_Final/EFI/BOOT/BOOTX64.ef i trusted.gfid=0xa9b0a66cf39b49c7890b2da3f631929f There are only 2 nodes in this gluster, it hasn't been used for long, its running gluster 3.4, it hasn't been messed with in any way as far as I'm aware, and yet gluster can't delete files that are right there staring it in the face. Mind-boggling. Should I re-send this to the gluster-devel mailing list? _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
