[Pkg-glusterfs-devel] Bug#555541: glusterfs-client: Support for proper client mounting via fstab at startup

[Jan Villeminot]

Package: glusterfs-client
Version: 2.0.7-0.0.1
Severity: wishlist

When starting up, Debian fails to mount the glusterfs partitions present
on fstab.

In fact, glusterfs does not find fuse because the mountall and
other init script related to mounting partitions are ran before fuse starts
up. 

After investigation, it appears that the information set within the 
comment header of fuse, and the lack of init script for glusterfs-client, 
causes insserv to attempt mounting the glusterfs volumes set in /etc/fstab 
before FUSE is operational.

On servers without insserv, fuse seems to start up before the mount*
init scripts ; which is correct.

The problem is that no init scripts are included in the glusterfs-client
package to prevent insserv from starting fuse after the mount* init scripts.
Furthermore, when the machine runs as a glusterfs client, FUSE's init comment
header should be overridden, as now FUSE should not depend on $remote_fs, but
provide it (through Glusterfs).

        -- Jan

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (800, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages glusterfs-client depends on:
ii  fuse-utils                   2.7.4-2     Filesystem in USErspace (utilities
ii  glusterfs-server             2.0.7-0.0.1 clustered file-system

glusterfs-client recommends no packages.

Versions of packages glusterfs-client suggests:
ii  glusterfs-examples           2.0.7-0.0.1 example files for the glusterfs se

-- no debconf information