Bug 763780 (GLUSTER-2048) - Odd behavior device or resource busy
Summary: Odd behavior device or resource busy
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-2048
Product: GlusterFS
Classification: Community
Component: core
Version: 3.1.0
Hardware: All
OS: Windows
low
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-02 15:46 UTC by Jacob Shucart
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

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.


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