Bug 805668

Summary: mount.glusterfs won't auto mount gluster filesystems from /etc/fstab on boot even with the auto mount option
Product: Red Hat Gluster Storage Reporter: csb sysadmin <admin>
Component: glusterfsAssignee: Amar Tumballi <amarts>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: gluster-bugs, ndevos, shaines, ssaha, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-29 08:52:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description csb sysadmin 2012-03-21 18:56:08 UTC
Description of problem:

mount.glusterfs won't automatically mount gluster filesystems from /etc/fstab on boot even when the fstab line looks like this :

gluster1:/pirdist       /pirdist                glusterfs transport=tcp,auto        0 0

Version-Release number of selected component (if applicable):

3.2.5

How reproducible:

Always


Steps to Reproduce:
1. Create a line in /etc/fstab for the gluster filesystem and mount point with or without the auto mount option.
2. Reboot system
3. Gluster filesystems are not mounted after boot.
  
Actual results:

Gluster filesystems from /etc/fstab are not mounted after boot

Expected results:

Gluster filesystems from /etc/fstab should be automatically mounted after boot by default, and especially so if the "auto" option exists and is used if you guys decide to not make it the default behavior.

Additional info:

Currently have "mount /pirdist" in /etc/rc.local and that seems to be a reasonable workaround.

Comment 1 Amar Tumballi 2012-05-02 16:28:58 UTC
this needs a '_netdev' option too in the line. Please let us know if providing '_netdev' in /etc/fstab helps or not.

Comment 5 Niels de Vos 2012-07-10 06:32:05 UTC
This only affects glusterfs-3.2.x (RHSSA-3.2). This issue is resolved in glusterfs-3.3 (in RHS-2.0).

Comment 6 Amar Tumballi 2012-10-29 08:52:04 UTC
we are not working on fixing any issues on RHSSA-3.2. Will close the bug as WONTFIX.