Bug 1565643 - Rebalance process failed to lock the file resulting in file migration failure
Summary: Rebalance process failed to lock the file resulting in file migration failure
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribute
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nithya Balachandran
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-10 13:09 UTC by Prasad Desala
Modified: 2018-11-19 05:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:24:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Prasad Desala 2018-04-10 13:09:30 UTC
Description of problem:
=======================
Rebalance process failed to lock the file which resulted to migration failure.

[2018-04-10 11:26:01.931895] W [MSGID: 109023] [dht-rebalance.c:1575:dht_migrate_file] 0-distrepx3-dht: migrate file failed: /linux-4.9.27/Documentation/arm64/booting.txt: failed to lock file on distrepx3-replicate-4 [Stale file handle]
[2018-04-10 11:26:01.932070] E [MSGID: 109023] [dht-rebalance.c:2735:gf_defrag_migrate_single_file] 0-distrepx3-dht: migrate-data failed for /linux-4.9.27/Documentation/arm64/booting.txt [Stale file handle]

Version-Release number of selected component (if applicable):
3.12.2-7.el7rhgs.x86_64

How reproducible:
1/1

Steps to Reproduce:
===================
1) Create a x3 volume and start it.
2) FUSE mount it on multiple clients.
3) Start below ops from clients,
- Client-1 Start linux kernel untar
- Client-2 and 3 start lookups
- Client-4 while true; do du -h /mnt/distrepx3_new;done
4) While step-3 is in-progress, start add-brick and trigger rebalance.
5) Wait till the rebalance completes.

Actual results:
==============
Rebalance process failed to lock the file which resulted to migration failure

Expected results:
=================
All the files should be migrated without any failures.


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