Bug 761904 (GLUSTER-172)

Summary: [ glusterfs 2.0.6rc1 ] - "Cannot open: Device or resource busy" on tar extraction
Product: [Community] GlusterFS Reporter: Vinayak Hegde <vinayak>
Component: stripeAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 2.0.5CC: gluster-bugs, guru, lakshmipathi, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTA Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vinayak Hegde 2009-07-29 07:38:41 UTC
3 servers with stripe
write-behind and io-cache on client side

trying to run kernel_compile tar extraction


Extracting Tarball ..
tar: linux-2.6.30.3/arch/arm/boot: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/arm/boot/.gitignore: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/arm/boot/Makefile: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/arm/boot/bootp: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/arm/boot/bootp/Makefile: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/arm/boot/bootp/bootp.lds: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/ia64/dig: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/devboards/db1x00: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/devboards/db1x00/Makefile: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/devboards/db1x00/board_setup.c: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/devboards/db1x00/irqmap.c: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/devboards/pb1100: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/devboards/pb1100/Makefile: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/mtx-1: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/mtx-1/Makefile: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/mtx-1/board_setup.c: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/mtx-1/init.c: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/alchemy/xxs1500: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi: Cannot mkdir: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/gio.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/hpc3.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/ioc.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/ip22.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/mc.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/pi1.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/seeq.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/sgi.h: Cannot open: Device or resource busy
tar: linux-2.6.30.3/arch/mips/include/asm/sgi/wd.h: Cannot open: Device or resource busy
 tar: Error exit delayed from previous errors

Comment 1 Amar Tumballi 2009-07-30 21:45:52 UTC
(In reply to comment #0)
> 3 servers with stripe
> write-behind and io-cache on client side
> 
> trying to run kernel_compile tar extraction
> 
> 
> Extracting Tarball ..
> tar: linux-2.6.30.3/arch/arm/boot: Cannot mkdir: Device or resource busy

You were running operation on just one client? and were there any 'rm -rf' or similar operations going on over the mountpoint??  The EBUSY error comes by fuse driver itself..

Can you try running:
 
 bash# echo 3 > /proc/sys/vm/drop_caches

and trying to tar extract again??

Comment 2 Amar Tumballi 2009-07-31 19:41:07 UTC
Hi Vinayak,
 Can you try by doing a LD_PRELOAD of the code at http://git.gluster.com/?p=users/amar/fuse-mkdir.git;a=summary and trying the extraction again??

With this we can make sure its not 'fuse' issue..

Comment 3 Amar Tumballi 2009-11-11 18:07:52 UTC
With inode generation ENODEV/EBUSY is gone, and we have more stripe related bugs open. closing this one.