Bug 1385440 - Gluster 3.7.16 & Samba Issues
Summary: Gluster 3.7.16 & Samba Issues
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: 3.7.15
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Adam
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 03:06 UTC by Ryan Mills
Modified: 2017-03-08 10:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:48:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ryan Mills 2016-10-17 03:06:03 UTC
Description of problem:
Utilizing Samba or Samba-VFS-Modules, Gluster 3.7.16 appears to have issues with allowing Read/Writes of a file on the cluster from a windows machine.
From a Windows machine it receives "A Network error has occured" when reading/writing a file.

Load is also extremely high since 3.7.16 upgrade.
Checking Brick logs there are spammed amounts of these;
http://paste.ubuntu.com/23336873/
When we installed and checked 'htop' there was one process using 100% of one core.
Once killed Load balanced out again

Version-Release number of selected component (if applicable):
glusterfs 3.7.16 built on Oct 11 2016 14:02:29
Version 4.3.11-Ubuntu

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:        14.04
Codename:       trusty


How reproducible:
Install 3.7.16 and Share a Path out via Samba or Samba-VFS-Modules
Try to read/write a file from a windows client

Actual results:
"A Network error has occured"

Expected results:
Files should allow Read/Writes

Additional info:

Have increased logging on Samba but really the only consistent error I can find is - http://paste.ubuntu.com/23336877/
I mean even when I stop using samba-vfs-modules and just have a direct mountpoint I get the same issue.
log.smbd - http://paste.ubuntu.com/23336705/

Comment 1 Kaushal 2017-03-08 10:48:49 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.