On Fri, 2016-01-29 at 18:59 +0530, PankaJ Singh wrote: > Hi, > > Thanks Anoop for the help, > Would you please tell me when can we expect this new release with > this bug fix. > Please find the corresponding patch posted for mainline at [1]. I am not sure whether we can back port the same and include it for 3.7.8. I will update the thread asap. [1] https://review.gluster.org/#/c/13346/ --Anoop C S. > > Thanks & Reagrds > > > > On Fri, Jan 29, 2016 at 12:42 PM, Anoop C S <anoopcs@xxxxxxxxxx> > wrote: > > On Wed, 2016-01-27 at 15:25 +0530, PankaJ Singh wrote: > > > > > > Hi, > > > > > > We are using gluster 3.7.6 on ubuntu 14.04. We are facing an > > issue > > > with trashcan feature. > > > Our scenario is as follow: > > > > > > 1. 2 node server (ubuntu 14.04 with glusterfs 3.7.6) > > > 2. 1 client node (ubuntu 14.04) > > > 3. I have created one volume vol1 with 2 bricks in replica and > > with > > > transport = tcp mode. > > > 4. I have enabled quota on vol1 > > > 5. Now I have enabled trashcan feature on vol1 > > > 6. Now I have mounted vol1 on client's home directory "mount -t > > > glusterfs -o transport=tcp server-1:/vol1 /home/" > > > 7. Now when I logged in via any existing non-root user and > > perform > > > any editing via vim editor then I getting this error "E200: > > *ReadPre > > > autocommands made the file unreadable" and my user's home > > > directory permission get changed to 000. after sometime these > > > permission gets revert back automatically. > > > > > > (NOTE: user's home directories are copied in mounted directory > > > glusterfs volume vol1) > > > > > > > As discussed over irc, we will definitely look into this issue [1] > > and > > get back asap. On the other side, I have some solid reasons in > > recommending not to use swap/backup files, created/used by Vim, > > when > > trash is enabled for a volume (assuming you have the basic vimrc > > config > > where swap/backup files are enabled by default): > > > > 1. You will see lot of foo.swpx/foo.swp files (with time stamp > > appended > > in their filenames) inside trashcan as Vim creates and removes > > these > > swap files every now and then. > > > > 2. Regarding backup files, you will notice a list of 4913 named > > files > > inside .trashcan. These files are created and deleted by Vim to > > make > > sure that it can create files in the current directory. And of > > course every time you save it with :w. > > > > 3. Similar is the case with undo files like .foo.un~. > > > > 4. Last but not the least, every time you do a :w, Vim performs a > > truncate operation which will cause the previous version of file > > to > > be moved to .trashcan. > > > > Having said that, you can insert the following lines to your vimrc > > file > > to prevent those unnecessary files, described through first 3 > > points, > > to land inside .trashcan. > > > > set noundofile > > set noswapfile > > set nobackup > > set nowritebackup > > > > As per the current implementation, we cannot prevent previous > > versions > > of file being created inside trash directory and I think these > > files > > will serve as backup files for future which is a good to have > > feature. > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1302307 > > > > --Anoop C S > > > > > > > > Thanks & Regards > > > PankaJ Singh > > > _______________________________________________ > > > Gluster-users mailing list > > > Gluster-users@xxxxxxxxxxx > > > http://www.gluster.org/mailman/listinfo/gluster-users > > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
