Suggestions on implementing trash translator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

There are some issues we are dealing with trash translator(see attachment for design doc).In our implementation, we create trash directory using trash translator.Thus trash directories on different bricks will have different gfids.A gfid conflict will arise.

* To deal with gfid issue we tried to create trash directory using posix translator and set fixed gfid for trash directory.And gfid conflict was solved.Is this solution feasible?

* Trash directory is a configurable option by trash translator from cli.So when we perform volume set for changing the trash directory,it will be available in trash translator's dictionary.It is not passed to posix translator(every translator will have different dictionaries for them).The only way is to make configurable option as part of posix translator.Is this a right way of implementation?

* When a trash directory is reconfigured from cli  , whether we need to perform a rename operation from old trash directory to new one or just create new trash directory?


To summarize , we trying to make posix translator as the owner of trash directory and trash translator will intercept fops like unlink,truncate .
What are your suggestions for it?   

Attachment: desig-doc.pdf
Description: Adobe PDF document

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux