Bug 761780 (GLUSTER-48)

Summary: lockup after mounting glusterfs volume on /usr
Product: [Community] GlusterFS Reporter: Basavanagowda Kanur <gowda>
Component: protocolAssignee: Vijay Bellur <vbellur>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: amarts, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Basavanagowda Kanur 2009-06-24 18:01:00 UTC
[Migrated from savannah BTS] - bug 25910 [https://savannah.nongnu.org/bugs/?25910]
Wed 18 Mar 2009 09:45:24 AM GMT, original submission by Krzysztof Strasburger <strasbur>:

Trying to mount the glusterfs volume (replicated on 13 nodes,
if it matters) results in lockup of every process trying to
access the newly mounted /usr directory. The mount program returns
success, but there are no signs of client connection in the
server logfile (monitored with tail -f during mounting).
Trying to umount /usr immediately after mounting ends with "/usr
is busy". Glusterfs and libfuse are compiled with --prefix=/
and monitoring the mounting process with strace -f indicates no
access to files in /usr, except of early (and successful) runs
of sed and grep. The same volume can be mounted without problems
on "less important" directories. Is it a glusterfs problem
or a general fuse issue? BTW, the same problem occurs with
2.0.0rc2 (earlier versions not checked).
--------------------------------------------------------------------------------

Thu 19 Mar 2009 08:44:34 AM GMT, comment #1 by 	Krzysztof Strasburger <strasbur>:

I'm able to mount /usr with glusterfs-1.3.12, but it works for
a while only and lockup occurs later at a random moment. So,
the problem seems to be glusterfs related and probably 2.0.0
exposed an older bug.

Comment 1 Amar Tumballi 2009-11-26 03:17:44 UTC
making it resolved with "won't fix" for now. If the issue prevails with 3.0.0 release, lets work on it then.