| 2013-07-25 19:56:43 |
Bruno MACADRE |
bug |
|
|
added bug |
| 2013-07-25 19:57:41 |
Bruno MACADRE |
description |
I've two servers replicating data by Gluster every servers are clients too.
The problem is that the glusterfs was never mounted at boot 'cause mountall doesn't call correct mount command and doesn't treat gluster filesystem as remote filesystem.
Some informations :
# lsb_realease -rd
Description: Ubuntu 13.04
Release: 13.04
# apt-cache policy mountall
mountall:
Installed : 2.48build1
Candidate : 2.48build1
Table de version :
*** 2.48build1 0
500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status
# mountall --version
mountall 2.44
Entry in the fstab :
192.162.0.1:test-vol /srv/conf glusterfs defaults,_netdev 0 0
After boot, this entry wasn't mounted. But if I try :
# mount -t glusterfs 192.162.0.1:test-vol /srv/test-vol
It works perfectly
I put a '--verbose' into /etc/init/mountall.conf file to see what happend. I obtain this :
/ est local
/proc est virtual
/sys est virtual
/sys/fs/cgroup est virtual
/sys/fs/fuse/connections est virtual
/sys/kernel/debug est virtual
/sys/kernel/security est virtual
/dev est virtual
/dev/pts est virtual
/tmp est local
/run est virtual
/run/lock est virtual
/run/shm est virtual
/run/user est virtual
/srv est local
/var est local
UUID=ac001a41-9a55-49d6-86c8-1e9e8df41054 est swap
/mnt/shared-conf est local
/srv/conf est nowait <== Why not remote ?
mounting event sent for /sys/fs/cgroup
mounting event sent for /sys/fs/fuse/connections
mounting event sent for /sys/kernel/debug
mounting event sent for /sys/kernel/security
mounting event sent for /run/lock
mounting event sent for /run/shm
mounting event sent for /run/user
...
mounting event handled for /srv/conf
montage de /srv/conf
mounted event handled for /srv/conf
local 5/5 remote 0/0 virtual 12/12 swap 1/1
^
And no /srv/conf mounted...
With this command I've found more information :
# mountall --verbose
...
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11156] s'est terminé normalement
...
We can see that the call of mount was not correct (see Usage).
If I go deeper :
# mountall --verbose --debug
...
run_mount: mtab /srv/conf
spawn: mount -f -t fuse.glusterfs -o defaults,_netdev 10.130.163.253:volume-conf /srv/conf
spawn: mount /srv/conf [11339]
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11339] s'est terminé normalement
...
When I try the mount mentioned above I've got the same behaviour (send Usage) 'cause fuse.glusterfs wasn't recognized. If I put glusterfs instead the mount works as expected.
More, since mountall doesn't treat glusterfs as remote filesystem, it try to mount it even if local filsystems aren't mounted yet. For example, if /var wasn't cleanly unmounted, it will be checked at boot and mountall try to mount glusterfs during check. This cause some troubles because glusterfsd need acces to /var/log which is not mounted yet... |
I've two servers replicating data by Gluster every servers are clients too.
The problem is that the glusterfs was never mounted at boot 'cause mountall doesn't call correct mount command and doesn't treat gluster filesystem as remote filesystem.
Some informations :
# lsb_realease -rd
Description: Ubuntu 13.04
Release: 13.04
# apt-cache policy mountall
mountall:
Installed : 2.48build1
Candidate : 2.48build1
Table de version :
*** 2.48build1 0
500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status
# mountall --version
mountall 2.44
Entry in the fstab :
192.162.0.1:test-vol /srv/conf glusterfs defaults,_netdev 0 0
After boot, this entry wasn't mounted. But if I try :
# mount -t glusterfs 192.162.0.1:test-vol /srv/test-vol
It works perfectly
I put a '--verbose' into /etc/init/mountall.conf file to see what happend. I obtain this :
/ est local
/proc est virtual
/sys est virtual
/sys/fs/cgroup est virtual
/sys/fs/fuse/connections est virtual
/sys/kernel/debug est virtual
/sys/kernel/security est virtual
/dev est virtual
/dev/pts est virtual
/tmp est local
/run est virtual
/run/lock est virtual
/run/shm est virtual
/run/user est virtual
/srv est local
/var est local
UUID=ac001a41-9a55-49d6-86c8-1e9e8df41054 est swap
/mnt/shared-conf est local
/srv/conf est nowait <== Why not remote ?
mounting event sent for /sys/fs/cgroup
mounting event sent for /sys/fs/fuse/connections
mounting event sent for /sys/kernel/debug
mounting event sent for /sys/kernel/security
mounting event sent for /run/lock
mounting event sent for /run/shm
mounting event sent for /run/user
...
mounting event handled for /srv/conf
montage de /srv/conf
mounted event handled for /srv/conf
local 5/5 remote 0/0 virtual 12/12 swap 1/1
^
And no /srv/conf mounted...
With this command I've found more information :
# mountall --verbose
...
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11156] s'est terminé normalement
...
We can see that the call of mount was not correct (see Usage).
If I go deeper :
# mountall --verbose --debug
...
run_mount: mtab /srv/conf
spawn: mount -f -t fuse.glusterfs -o defaults,_netdev 10.130.163.253:volume-conf /srv/conf
spawn: mount /srv/conf [11339]
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11339] s'est terminé normalement
...
When I try the mount mentioned above I've got the same behaviour (send Usage) 'cause fuse.glusterfs wasn't recognized. If I put glusterfs instead the mount works as expected.
More, since mountall doesn't treat glusterfs as remote filesystem, it try to mount it even if local filsystems aren't mounted yet. For example, if /var wasn't cleanly unmounted, it will be checked at boot and mountall try to mount glusterfs during check. This cause some troubles because glusterfsd need acces to /var/log which is not mounted yet... |
|
| 2013-07-25 19:57:52 |
Bruno MACADRE |
description |
I've two servers replicating data by Gluster every servers are clients too.
The problem is that the glusterfs was never mounted at boot 'cause mountall doesn't call correct mount command and doesn't treat gluster filesystem as remote filesystem.
Some informations :
# lsb_realease -rd
Description: Ubuntu 13.04
Release: 13.04
# apt-cache policy mountall
mountall:
Installed : 2.48build1
Candidate : 2.48build1
Table de version :
*** 2.48build1 0
500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status
# mountall --version
mountall 2.44
Entry in the fstab :
192.162.0.1:test-vol /srv/conf glusterfs defaults,_netdev 0 0
After boot, this entry wasn't mounted. But if I try :
# mount -t glusterfs 192.162.0.1:test-vol /srv/test-vol
It works perfectly
I put a '--verbose' into /etc/init/mountall.conf file to see what happend. I obtain this :
/ est local
/proc est virtual
/sys est virtual
/sys/fs/cgroup est virtual
/sys/fs/fuse/connections est virtual
/sys/kernel/debug est virtual
/sys/kernel/security est virtual
/dev est virtual
/dev/pts est virtual
/tmp est local
/run est virtual
/run/lock est virtual
/run/shm est virtual
/run/user est virtual
/srv est local
/var est local
UUID=ac001a41-9a55-49d6-86c8-1e9e8df41054 est swap
/mnt/shared-conf est local
/srv/conf est nowait <== Why not remote ?
mounting event sent for /sys/fs/cgroup
mounting event sent for /sys/fs/fuse/connections
mounting event sent for /sys/kernel/debug
mounting event sent for /sys/kernel/security
mounting event sent for /run/lock
mounting event sent for /run/shm
mounting event sent for /run/user
...
mounting event handled for /srv/conf
montage de /srv/conf
mounted event handled for /srv/conf
local 5/5 remote 0/0 virtual 12/12 swap 1/1
^
And no /srv/conf mounted...
With this command I've found more information :
# mountall --verbose
...
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11156] s'est terminé normalement
...
We can see that the call of mount was not correct (see Usage).
If I go deeper :
# mountall --verbose --debug
...
run_mount: mtab /srv/conf
spawn: mount -f -t fuse.glusterfs -o defaults,_netdev 10.130.163.253:volume-conf /srv/conf
spawn: mount /srv/conf [11339]
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11339] s'est terminé normalement
...
When I try the mount mentioned above I've got the same behaviour (send Usage) 'cause fuse.glusterfs wasn't recognized. If I put glusterfs instead the mount works as expected.
More, since mountall doesn't treat glusterfs as remote filesystem, it try to mount it even if local filsystems aren't mounted yet. For example, if /var wasn't cleanly unmounted, it will be checked at boot and mountall try to mount glusterfs during check. This cause some troubles because glusterfsd need acces to /var/log which is not mounted yet... |
I've two servers replicating data by Gluster every servers are clients too.
The problem is that the glusterfs was never mounted at boot 'cause mountall doesn't call correct mount command and doesn't treat gluster filesystem as remote filesystem.
Some informations :
# lsb_realease -rd
Description: Ubuntu 13.04
Release: 13.04
# apt-cache policy mountall
mountall:
Installed : 2.48build1
Candidate : 2.48build1
Table de version :
*** 2.48build1 0
500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status
# mountall --version
mountall 2.44
Entry in the fstab :
192.162.0.1:test-vol /srv/conf glusterfs defaults,_netdev 0 0
After boot, this entry wasn't mounted. But if I try :
# mount -t glusterfs 192.162.0.1:test-vol /srv/test-vol
It works perfectly
I put a '--verbose' into /etc/init/mountall.conf file to see what happened. I obtain this :
/ est local
/proc est virtual
/sys est virtual
/sys/fs/cgroup est virtual
/sys/fs/fuse/connections est virtual
/sys/kernel/debug est virtual
/sys/kernel/security est virtual
/dev est virtual
/dev/pts est virtual
/tmp est local
/run est virtual
/run/lock est virtual
/run/shm est virtual
/run/user est virtual
/srv est local
/var est local
UUID=ac001a41-9a55-49d6-86c8-1e9e8df41054 est swap
/mnt/shared-conf est local
/srv/conf est nowait <== Why not remote ?
mounting event sent for /sys/fs/cgroup
mounting event sent for /sys/fs/fuse/connections
mounting event sent for /sys/kernel/debug
mounting event sent for /sys/kernel/security
mounting event sent for /run/lock
mounting event sent for /run/shm
mounting event sent for /run/user
...
mounting event handled for /srv/conf
montage de /srv/conf
mounted event handled for /srv/conf
local 5/5 remote 0/0 virtual 12/12 swap 1/1
^
And no /srv/conf mounted...
With this command I've found more information :
# mountall --verbose
...
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11156] s'est terminé normalement
...
We can see that the call of mount was not correct (see Usage).
If I go deeper :
# mountall --verbose --debug
...
run_mount: mtab /srv/conf
spawn: mount -f -t fuse.glusterfs -o defaults,_netdev 10.130.163.253:volume-conf /srv/conf
spawn: mount /srv/conf [11339]
Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT]
or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT]
Try `glusterfs --help' or `glusterfs --usage' for more information.
mount /srv/conf [11339] s'est terminé normalement
...
When I try the mount mentioned above I've got the same behaviour (send Usage) 'cause fuse.glusterfs wasn't recognized. If I put glusterfs instead the mount works as expected.
More, since mountall doesn't treat glusterfs as remote filesystem, it try to mount it even if local filsystems aren't mounted yet. For example, if /var wasn't cleanly unmounted, it will be checked at boot and mountall try to mount glusterfs during check. This cause some troubles because glusterfsd need acces to /var/log which is not mounted yet... |
|
| 2013-07-25 22:22:17 |
Steve Langasek |
marked as duplicate |
|
1103047 |
|
| 2013-07-26 06:02:59 |
Bruno MACADRE |
removed duplicate marker |
1103047 |
|
|
| 2013-09-15 18:01:54 |
Launchpad Janitor |
mountall (Ubuntu): status |
New |
Confirmed |
|
| 2013-09-26 18:35:06 |
Paul Boven |
bug |
|
|
added subscriber Paul Boven |
| 2013-09-26 20:09:45 |
Steve Langasek |
affects |
mountall (Ubuntu) |
glusterfs (Ubuntu) |
|
| 2014-06-19 13:00:37 |
J. Pablo Fernández |
bug |
|
|
added subscriber J. Pablo Fernández |
