Bug 1080988 - AFR V2 : kernel untar on fuse/nfs mount fails when a brick goes offline
Summary: AFR V2 : kernel untar on fuse/nfs mount fails when a brick goes offline
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-26 12:48 UTC by spandura
Modified: 2016-01-11 09:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-01-11 09:42:58 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description spandura 2014-03-26 12:48:48 UTC
Description of problem:
======================
On a replicate volume with 3 bricks, running kernel untar on fuse/nfs mount fails with error : "Cannot open: Stale file handle ". 

Version-Release number of selected component (if applicable):
===========================================================
glusterfs 3git built on Mar 25 2014 05:20:53
Repository revision: git://git.gluster.com/glusterfs.git

How reproducible:
====================
Often

Steps to Reproduce:
===================
1. Create 1 x 3 replicate volume. Start the volume. 

2. Create a fuse and nfs mount from the client. 

3. 

From fuse mount execute:
~~~~~~~~~~~~~~~~~~~~~~~
mkdir test_fuse ; cd test_fuse ; mkdir test_kernel_untar_and_compilation ; cd test_kernel_untar_and_compilation ; wget -c http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.6-rc4.tar.gz ;  mkdir linux_kernel ; tar -zxvf linux-3.6-rc4.tar.gz -C linux_kernel ;

From nfs mount execute:
~~~~~~~~~~~~~~~~~~~~~~~
mkdir test_nfs ; cd test_nfs ; mkdir test_kernel_untar_and_compilation ; cd test_kernel_untar_and_compilation ; wget -c http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.6-rc4.tar.gz ;  mkdir linux_kernel ; tar -zxvf linux-3.6-rc4.tar.gz -C linux_kernel ;  

4. Bring down a brick ( xfs_progs/xfstests/src/godown <brick_mount_point> )

Actual results:
================
tar fails on the both the mount points:

tar: linux-3.6-rc4/arch/alpha/kernel/pci-sysfs.c: Cannot open: Stale file handle
linux-3.6-rc4/arch/alpha/kernel/pci.c
tar: linux-3.6-rc4/arch/alpha/kernel/pci.c: Cannot open: Stale file handle
linux-3.6-rc4/arch/alpha/kernel/pci_impl.h
tar: linux-3.6-rc4/arch/alpha/kernel/pci_impl.h: Cannot open: Stale file handle
linux-3.6-rc4/arch/alpha/kernel/pci_iommu.c
tar: linux-3.6-rc4/arch/alpha/kernel/pci_iommu.c: Cannot open: Stale file handle
linux-3.6-rc4/arch/alpha/kernel/perf_event.c
tar: linux-3.6-rc4/arch/alpha/kernel/perf_event.c: Cannot open: Stale file handle
linux-3.6-rc4/arch/alpha/kernel/process.c
tar: linux-3.6-rc4/arch/alpha/kernel/process.c: Cannot open: Stale file handle
linux-3.6-rc4/arch/alpha/kernel/proto.h
tar: linux-3.6-rc4/arch/alpha/kernel/proto.h: Cannot open: Stale file handle


Expected results:
=================
untar should be successful. 

Additional info:
=================
root@rhs-client11 [Mar-26-2014- 8:48:02] >gluster v info
 
Volume Name: vol_rep
Type: Replicate
Volume ID: 49001cac-32d9-461e-8432-647b46bb7a5a
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: rhs-client11:/rhs/bricks/vol_rep_b0
Brick2: rhs-client12:/rhs/bricks/vol_rep_b1
Brick3: rhs-client13:/rhs/bricks/vol_rep_b2
root@rhs-client11 [Mar-26-2014- 8:48:04] >


root@rhs-client12 [Mar-26-2014- 8:42:25] >gluster v status
Status of volume: vol_rep
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick rhs-client11:/rhs/bricks/vol_rep_b0		49152	Y	4179
Brick rhs-client12:/rhs/bricks/vol_rep_b1		49152	Y	29085
Brick rhs-client13:/rhs/bricks/vol_rep_b2		N/A	N	N/A
NFS Server on localhost					2049	Y	29527
Self-heal Daemon on localhost				N/A	Y	29536
NFS Server on 10.70.36.35				2049	Y	13036
Self-heal Daemon on 10.70.36.35				N/A	N	N/A
NFS Server on rhs-client13				2049	Y	4168
Self-heal Daemon on rhs-client13			N/A	Y	4177
 
Task Status of Volume vol_rep
------------------------------------------------------------------------------
There are no active volume tasks
 
root@rhs-client12 [Mar-26-2014- 8:42:29] >

Comment 1 spandura 2014-03-26 13:14:29 UTC
Subsequent "removal operation" of the files/dirs from mount point fails. 

Following are the errors observed:
===================================

rm: cannot remove `clients/client0/~dmtmp/PARADOX/COURSES.DB': Input/output error
rm: cannot remove `clients/client0/~dmtmp/PARADOX/COURSES.PX': Input/output error
rm: cannot remove `clients/client0/~dmtmp/PARADOX/COURSES.X04': Input/output error
rm: cannot remove `clients/client0/~dmtmp/PARADOX/COURSES.Y04': Input/output error
rm: cannot remove `clients/client0/~dmtmp/PARADOX/STUDENTS.DB': Input/output error
rm: cannot remove `clients/client0/~dmtmp/PARADOX/STUDENTS.PX': Input/output error
rm: cannot remove `clients/client0/~dmtmp/PARADOX/STUDENTS.XG0': Input/output error
rm: cannot remove `clients/client0/filler.000': Input/output error
rm: cannot remove `clients/client0/filler.001': Input/output error
rm: cannot remove `clients/client0/filler.002': Input/output error
rm: cannot remove `clients/client0/filler.003': Input/output error
rm: cannot remove `clients/client0/filler.004': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/STUDENTS.YG0': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/STUDENTS.XG1': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/STUDENTS.YG1': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/STUDENTS.VAL': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/STUDENTS.MB': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/ENROLL.DB': Input/output error
rm: cannot remove `clients/client7/~dmtmp/PARADOX/ENROLL.PX': Input/output error


rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/usb/spear-usb.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/usb/usb-ehci.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/virtio/mmio.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/watchdog/samsung-wdt.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/x86/ce4100.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/x86/interrupt.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/x86/timer.txt': Stale file handle
rm: cannot remove `test_fuse/test_kernel_untar_and_compilation/linux_kernel/linux-3.6-rc4/Documentation/devicetree/bindings/xilinx.txt': Stale file handle


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