gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gluster-devel] glusterfs -- mainline 2.5 -- patch 690 won't mount


From: Jordi Moles
Subject: [Gluster-devel] glusterfs -- mainline 2.5 -- patch 690 won't mount
Date: Mon, 03 Mar 2008 19:02:01 +0100
User-agent: Thunderbird 2.0.0.12 (X11/20080213)

hi,

through this mailing list and also the chat room in freenode, i was suggested to set up a system using this version of glusterfs, mainline 2.5 path 690.

the thing is that everything compiles and installs just fine.

On the node side, the daemons run with no problem. On the client side, however, i keep getting these messages:

**********

2008-03-03 17:52:55 E [fuse-bridge.c:2565:init] glusterfs-fuse: fuse_mount failed (No such file or directory)

2008-03-03 17:52:55 E [glusterfs.c:526:main] glusterfs: Initializing graph failed

**********

I've installed earlier versions from tla, the exact same process, and never had this problem.

the command to load the filesystem is "glusterfs -l /var/log/glusterfs/glusterfs.log -L WARNING -f /etc/glusterfs/glusterfs-client.vol /mnt/gluster/"

all the files in that command exist:

/var/log/glusterfs/glusterfs.log
/etc/glusterfs/glusterfs-client.vol
/mnt/gluster/

the content of the /etc/glusterfs/glusterfs-client.vol is:

***********

volume espai1
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.204
   option remote-subvolume espai
end-volume

volume espai2
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.205
   option remote-subvolume espai
end-volume

volume espai3
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.206
   option remote-subvolume espai
end-volume

volume espai4
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.207
   option remote-subvolume espai
end-volume

volume espai5
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.213
   option remote-subvolume espai
end-volume

volume espai6
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.214
   option remote-subvolume espai
end-volume

volume namespace1
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.204
   option remote-subvolume nm
end-volume

volume namespace2
   type protocol/client
   option transport-type tcp/client
   option remote-host 192.168.1.205
   option remote-subvolume nm
end-volume

volume grup1
   type cluster/afr
   subvolumes espai1 espai2
end-volume

volume grup2
   type cluster/afr
   subvolumes espai3 espai4
end-volume

volume grup3
   type cluster/afr
   subvolumes espai5 espai6
end-volume

volume nm
   type cluster/afr
   subvolumes namespace1 namespace2
end-volume

volume ultim
   type cluster/unify
   subvolumes grup1 grup2 grup3
   option scheduler rr
   option namespace nm
end-volume

***********

On the node side:

***********

volume esp
   type storage/posix
   option directory /mnt/compartit
end-volume

volume espai
   type features/posix-locks
   subvolumes esp
end-volume

volume nm
   type storage/posix
   option directory /mnt/namespace
end-volume

volume ultim
   type protocol/server
   subvolumes espai nm
   option transport-type tcp/server
   option auth.ip.espai.allow *
   option auth.ip.nm.allow *
end-volume

***********

what should i check?  what am i doing wrong?

Thanks.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]