[Bugs] [Bug 1302307] New: vim command is not working with trashcan feature of glusterfs
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jan 27 12:51:20 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1302307
Bug ID: 1302307
Summary: vim command is not working with trashcan feature of
glusterfs
Product: GlusterFS
Version: 3.7.6
Component: trash-xlator
Severity: high
Assignee: bugs at gluster.org
Reporter: pank.singh9191 at gmail.com
CC: bugs at gluster.org
Description of problem: vi or vim is not working with trashcan feature of
glusterfs via non-root user.
Version-Release number of selected component (if applicable): Glusterfs 3.7.6
How reproducible: You can reproduce by using following steps
Steps to Reproduce:
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 or vi editor then I am getting this error "E200: *ReadPre autocommands
made the file unreadable" and my user's home directory permission also get
changed to 000. After sometime this permission gets automatically back to
original one.
(NOTE: user's home directories are copied in mounted directory glusterfs volume
vol1. And user's home directory have user's specific permissions)
Actual results: got this error "E200: *ReadPre autocommands made the file
unreadable" while editing any file via vim or vi editor
Expected results: I should able to edit any file via vim or vi editor
Additional info: May be this issue related to vim working style format since
vim or vi have to create a swap file for editing.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list