1566221 – tar: stale file handle observed during untar operation when a brick is added

Bug 1566221 - tar: stale file handle observed during untar operation when a brick is added

Summary: tar: stale file handle observed during untar operation when a brick is added

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	GlusterFS
Classification:	Community
Component:	core
Sub Component:
Version:	mainline
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	medium
Target Milestone:	---
Assignee:	bugs@gluster.org
QA Contact:
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2018-04-11 19:36 UTC by Susant Kumar Palai
Modified:	2019-06-14 10:06 UTC (History)
CC List:	2 users (show)
Fixed In Version:	glusterfs-4.1
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-06-14 10:00:43 UTC
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Dependent Products:

Attachments	(Terms of Use)
mount log with TRACE output (8.49 MB, text/plain) 2018-04-11 19:36 UTC, Susant Kumar Palai	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

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.

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