Bug 763780 (GLUSTER-2048)

Summary:	Odd behavior device or resource busy
Product:	[Community] GlusterFS	Reporter:	Jacob Shucart <jacob>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	chrisw, gluster-bugs, vijay
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jacob Shucart 2010-11-02 15:46:44 UTC

Create a distribute volume and mount it as GlusterFS on 2 client systems.

On system-a, create a directory called "test".
On system-b, cd into the test directory.
On system-a, mv test test.2
On system-b, while still in the test directory create a file.  Then cd ..

If you then do an ls on system-b, you will see that test doesn't exist and test.2 does exist.  IF you then try to make the test directory on system-b, you get:

[root@jacobgfs31-s3 test]# mkdir test
mkdir: cannot create directory `test': Device or resource busy

You will then see that the "test" directory was still created.

Comment 1 Anand Avati 2010-11-09 09:14:10 UTC

This is a bug/feature of FUSE (specifically in linux) and beyond the scope of any fuse based filesystem to alter the behavior.