Bug 761901 (GLUSTER-169) - Replicate Fails, Subvolumes Work Fine - Fedora 8 2.6.26.8-57
Summary: Replicate Fails, Subvolumes Work Fine - Fedora 8 2.6.26.8-57
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-169
Product: GlusterFS
Classification: Community
Component: replicate
Version: 2.0.4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-27 19:28 UTC by Jonathan Steffan
Modified: 2010-03-02 11:11 UTC (History)
4 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 Anand Avati 2009-07-27 18:50:42 UTC
What IO are you performing over the mountpoint?

Comment 1 Jonathan Steffan 2009-07-27 19:28:18 UTC
Client config:

cluster/replicate -> {protocol/client, protocol/client}

[2009-07-27 13:14:24] D [fuse-bridge.c:279:fuse_loc_fill] fuse-bridge: failed to search parent for 0/(null) (2356735304)
[2009-07-27 13:14:24] W [fuse-bridge.c:1655:fuse_opendir] glusterfs-fuse: 145: OPENDIR (null) (fuse_loc_fill() failed)
ls: cannot open directory /path/to/directory: No such file or directory

If just protocol/client, the mount works.

# uname -a
Linux server 2.6.26.8-57.fc8 #1 SMP Thu Dec 18 19:19:45 EST 2008 i686 i686 i386 GNU/Linux

# rpm -q fuse fuse-libs fedora-release
fuse-2.7.4-1.fc8.glfs11
fuse-libs-2.7.4-1.fc8.glfs11
fedora-release-8-6.transition

glusterfs version 2.0.4 tag + http://patches.gluster.com/patch/742/

Comment 2 Jonathan Steffan 2009-07-27 21:08:25 UTC
We are running: ls -R

Comment 3 Anush Shetty 2009-09-03 02:43:41 UTC
Have you been facing this problem with 2.0.6 ? If so, could you please provide us the volume files of your setup.

Comment 4 Anush Shetty 2010-01-28 04:18:03 UTC
Any updates on this ? Are you still facing this issue in the recent releases ?

thanks,
Anush

Comment 5 Shehjar Tikoo 2010-03-02 08:11:57 UTC
This behaviour not seen in 3.0.x. Please reopen if you can reproduce


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