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