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.
Any update on this? Does this happen on latest master?
This is fixed by the patch https://review.gluster.org/#/c/19849. Closing the bug.