Bug 763148 (GLUSTER-1416) - No Such File Or Directory when Stat'ing Files with Full Path After Expending Gluster File system to another Server
Summary: No Such File Or Directory when Stat'ing Files with Full Path After Expending ...
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-1416
Product: GlusterFS
Classification: Community
Component: core
Version: 3.0.3
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-22 10:52 UTC by Idan Shinberg
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Idan Shinberg 2010-08-22 10:52:46 UTC
Overview :
Gluster Platform was Composed of 3 Gluster Server Nodes and 20 Clients.
Add A Fourth Server Node And remonuted al cclients for changes to take effect.

After That, Trying TO access A file via it's full path results in "no such file or directory".Only After I Access The File Manually by CD'ing to the dirs one by one , the file becomes accessible via it's full path on all clients

In Order To Temporary Resolve This , I Did ls -lR on the Directory Tree Mount-Point.

Steps to Reproduce:
1) Create A  Directory Tree with some files and subdirs , ( no more then 3 levels)
on top of 2 GlusterFs Server Nodes.
2) Add a 3rd Server Node.Make Changes to the config file and unmount and mount on The Client To see the Extra Space Added.
3) Try to stat ( ls -l ) a leaf file that existed previous to the storage expansion.

Expected Results :
File Info

Actual Results :
No Such File or Directory . Accessing The File by Cd'ing to the dirs , each level at a time will give proper results  and make the file available to stat() via it's full path on all clients

This Happend on Glusterfs 3.0.3 on Linux x86_64 , CentOS 5.2 , 2.6.18-92

Comment 1 Amar Tumballi 2010-10-05 09:22:12 UTC
Try with 3.1 releases and this should be fixed


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