Bug 761780 (GLUSTER-48) - lockup after mounting glusterfs volume on /usr
Summary: lockup after mounting glusterfs volume on /usr
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-48
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-24 18:01 UTC by Basavanagowda Kanur
Modified: 2009-11-26 06:17 UTC (History)
2 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 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.


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