+++ 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.
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.
Shishir, please mark this for a known issue (in migration guide) and then add the text.
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
This issue has been documented as an important note in the migration guide. Hence, closing the bug.