Bug 762485 (GLUSTER-753) - Chown results in "No such file or directory" when files are touched in the backend
Summary: Chown results in "No such file or directory" when files are touched in the ba...
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-753
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-24 06:49 UTC by Pavan Vilas Sondur
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Pavan Vilas Sondur 2010-03-24 03:52:58 UTC
Configuration when this issue was seen:
* 8 clients and 4 servers(all server processes on 1 machine)
* touch files in the backend
* chown files on the mount point on any of the clients. 

Chown fails with "no such file or directory"

Comment 1 Pavan Vilas Sondur 2010-03-24 06:49:30 UTC

Comment 2 Vijay Bellur 2010-05-06 06:28:18 UTC
Raghu, Can you please try to re-create this problem?

Comment 3 Raghavendra Bhat 2010-05-06 09:17:57 UTC
With "lookup-unhashed option by default on" patch it is fixed. Verified with 3.0.4. It is working fine.

Comment 4 Lakshmipathi G 2010-06-01 05:06:28 UTC
checked again with 4 servers and 1 client,bug still exists with 4 servers. (earlier - it was verified with 2 servers - 1 client  and passed) 

chown: cannot access `/home/laks/workpath/regression/753/regr/mnt/client1/f1.txt': No such file or directory

Comment 5 Vijay Bellur 2010-06-07 04:46:05 UTC
Moving this to 3.0.6 since performing any activity on the backend is not recommended.

Comment 6 Amar Tumballi 2010-10-05 07:40:41 UTC
This should be gone with 3.1 releases. Raghu, I will be closing the bug. If you get the issue.. please reopen the bug. (This can be marked 'WONTFIX', as operations are done on backend).


Note You need to log in before you can comment on or make changes to this bug.