Replies: 1 comment
-
I think the indices are deleted on the next crawl by shd whenever that happens.
There should be no situation where a modification on posix xlator is done but the index for that gfid is not present. To achieve this, index is added first before a pre-operation is done on the inode and deleted after the post-operation is complete.
These are the base index files other gfid-strings link to. So they will always be present for use by index xlator.
|
Beta Was this translation helpful? Give feedback.
-
hi, thanks for making dev-session. these day, I saw the video dev-session 9, there are some questions I am not sure.
xattorp
, if some files are created at the beginning and then deleted, the file information will still be preserved, although this information will not be used.Here are the steps to reproduce the problem:
1). create a volume and mount
2). kill one of the brick pid
3). touch some files and make some directories
4). delete the files and directories what you made before.
5). use command
tree
to check path.glusterfs/indices
infohere you can find that the info about files and directories you made before were exists.
I don't know if the files were deleted , why do the info in
xattrop
still exists.you said for each posix request ,firstly it will make the index info in
.glusterfs/indices
to make sure that don't miss any requests, right ?In this part, I didn't listen carefully about it beacuse my english is not good . Could you summary the info about it ?
I don't know what the purpose of these documents is and their names will not change.
thanks .
Beta Was this translation helpful? Give feedback.
All reactions