[Gluster-users] rogue file

[Ted Miller]

A multi-part question relating to a scenario where a rogue program/person 
writes a file into a brick through the underlying file system (e.g. XFS) 
without going through glusterfs?

1. What is gluster supposed to do when a non-gluster file (no gluster xattrs) 
appears on a gluster brick?

2. What does the current implementation actually do?

3. Does it matter whether it is or is not a replicated brick?

4. Does it matter whether it is a striped brick?


Thinking about these scenarios after the file has been written:

A. No one ever looks at the file
B. A self-heal runs
C. A directory read gets done on that sub-directory
D. Someone actually tries to read the file (like if it was called readme.txt 
or some other common name)

Don't have an example at hand, just wondering what would happen as I work on 
putting together a test bed that will be either replica 2 or replica 4, 
unstriped.

Ted Miller
Elkhart, IN, USA