Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1566221

Summary: tar: stale file handle observed during untar operation when a brick is added
Product: [Community] GlusterFS Reporter: Susant Kumar Palai <spalai>
Component: coreAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: atumball, bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-4.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-14 10:00:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
mount log with TRACE output none

Description Susant Kumar Palai 2018-04-11 19:36:54 UTC 
Created attachment 1420511 [details]
mount log with TRACE output

Description of problem:
"Stale file handle" warnings are seen while doing untar operation when a new brick is added. Though untar operation does not break.

Volume type: I started with a single brick, plain distributed volume.


How reproducible:
All the time.

Steps to Reproduce:
1. Create a distributed volume
2. Start Linux untar (any untar)
3. Add-brick

Untar Output:
nux-4.16/Documentation/ABI/testing/sysfs-block
linux-4.16/Documentation/ABI/testing/sysfs-block-bcache
linux-4.16/Documentation/ABI/testing/sysfs-block-device
linux-4.16/Documentation/ABI/testing/sysfs-block-dm
linux-4.16/Documentation/ABI/testing/sysfs-block-rssd
linux-4.16/Documentation/ABI/testing/sysfs-block-zram
linux-4.16/Documentation/ABI/testing/sysfs-bus-acpi
linux-4.16/Documentation/ABI/testing/sysfs-bus-amba
linux-4.16/Documentation/ABI/testing/sysfs-bus-bcma
tar: linux-4.16/Documentation/ABI/testing/sysfs-bus-bcma: Cannot open: Stale file handle
linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10
tar: linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10: Cannot open: Stale file handle
linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x
tar: linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x: Cannot open: Stale file handle
linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x
tar: linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-etm4x: Cannot open: Stale file handle
linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel
tar: linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel: Cannot open: Stale file handle
linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-stm
linux-4.16/Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc


Have attached mount log with TRACE log level.



Additional info:
Try on commit 2bb17551a597b382d77bb5ebc2671b45565cd542 in master branch to reproduce this bug. With latest commit master, untar errors out and is getting fixed by https://review.gluster.org/#/c/19849. So either checkout to commit 2bb17551a597b382d77bb5ebc2671b45565cd542 or pull in the above patch to reproduce the issue.
Comment 1 Amar Tumballi 2019-06-14 09:55:49 UTC 
Any update on this? Does this happen on latest master?
Comment 2 Susant Kumar Palai 2019-06-14 10:00:43 UTC 
This is fixed by the patch https://review.gluster.org/#/c/19849. Closing the bug.