Bug 1357695 - fuse mount break when glusterfs is in striping configuration
Summary: fuse mount break when glusterfs is in striping configuration
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: 3.7.13
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Niels de Vos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-18 22:52 UTC by Carsten Feuls
Modified: 2017-03-08 10:58 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:58:26 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Carsten Feuls 2016-07-18 22:52:28 UTC
Description of problem:
I have tested GLusterFS with several modes.
But when GLusterFS is running in Striping mode. The fuse mount on the client
hangs when I copy some data.
The time when the fuse mount starts to hang vary from test to test.
I have reproduced it several times.

When GlusterFS is in Replication Mode or in Distribution Mode the Fuse mount work.


Version-Release number of selected component (if applicable):
Distributon: ArchLinux with all updates Installed.
glusterfs: 3.7.13
fuse: 2.9.7
Kernel: 4.6.4


How reproducible:
always

Steps to Reproduce:
1. Create GlusterFS in Striping Mode over 3 Nodes.
2. mount the glusterfs with the native client.
3. Try to copy some data in the cluster. FUSE mount will fail.



Actual results:
Fuse Mount hang after some data copied.


Expected results:
The Copy of the data should written to the cluster without hanging of Fuse mount.

Comment 1 Kaushal 2017-03-08 10:58:26 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.


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