Bug 852581

Summary: After the upgrade from glusterfs 3.2 to 3.3, the content of stipe and distributed-stripe is not available in mounted directory
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vidya Sakar <vinaraya>
Component: doc-Migration_GuideAssignee: Anjana Suparna Sriram <asriram>
Status: CLOSED CURRENTRELEASE QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: amarts, divya, gluster-bugs, mhideo, rfortier, rhinduja, rhs-bugs, storage-doc, vbellur, vinaraya
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 840737 Environment:
Last Closed: 2013-02-19 09:59:00 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:
Bug Depends On: 840737    
Bug Blocks:    

Description Vidya Sakar 2012-08-29 01:27:57 UTC 
+++ This bug was initially created as a clone of Bug #840737 +++

Description of problem:

After performing the migration from 3.2 glusterfs to 3.3 glusterfs, tried mounting the stripe and distributed stiped volumes. The data is not available in the mount directory.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Use glusterfs 3.2 and create the stripe and distributed-stripe volumes.
2. Mount these volumes and upload some data.
3. Upgrade the glusterfs version to 3.3
4. mount(using glusterfs or nfs) the stripe and distributed-stripe volume.
5. Data is not available to the mounted directory
  
Actual results:
Data is not available to the mounted directory

Expected results:

Data should be available

Additional info:
Confirmed that the data is available at the backend bricks.
Comment 2 Amar Tumballi 2012-10-22 07:17:48 UTC 
if we make sure we pass on only 'readdir()' calls down and not 'readdirp()' calls, this should work out...

people should perform 'ls -l' and the distribute should have 'use-readdirp=no' option, with md-cache(stat-prefetch) disabled. need to test this, and see if it  works. If works, can close this with a doc update.
Comment 3 Amar Tumballi 2012-12-24 09:38:32 UTC 
Shishir, please mark this for a known issue (in migration guide) and then add the text.
Comment 4 shishir gowda 2012-12-26 07:06:54 UTC 
As Amar mentioned, we need to update the migration doc to add this bug as a known issue. A work around to mention in the doc is as follows:

Before re-mounting the volume under 3.3
1. 'gluster volume set <volname> stat-prefetch off'
Mount with this xlator option enabled
2. --xlator-option *.use-readdirp=no
3. Run find . |xargs stat on the mount
4. After step 3 is completed, the volume can be used with stat-prefetch and doing a normal mount
Comment 5 Anjana Suparna Sriram 2013-02-19 09:59:00 UTC 
This issue has been documented as an important note in the migration guide. Hence, closing the bug.