|
From: | Ian Rogers |
Subject: | Re: [Gluster-devel] glusterfs entry in fstab |
Date: | Thu, 18 Mar 2010 14:32:22 +0000 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 |
On 18/03/2010 09:46, Amar Tumballi wrote:
Amar's suggestion is good if you have the vol definitions on the client. We have 2 bricks and lots of clients, so it's more convenient to keep the vol config on the bricks. The fstab entry can then be (in our case) brick.my.domain:data_scripts /data/scripts glusterfs disable-direct-io-mode,noatime 0 0 [aside: We also use dynamic dns to keep "brick.my.domain" up to date.] In /etc/glusterfs/glusterfsd.vol have something like volume dir_data_scripts type storage/posix option directory /gfs/data/scripts/export end-volume volume lock_data_scripts type features/locks subvolumes dir_data_scripts end-volume volume export_data_scripts type performance/io-threads option thread-count 128 # default is 1 subvolumes lock_data_scripts end-volume volume server-tcp type protocol/server option transport-type tcp option transport.socket.nodelay on option auth.addr.export_data_scripts.allow * option volume-filename.data_scripts /etc/glusterfs/data_scripts.vol subvolumes export_data_scripts end-volume We then put our client vol config in the file /etc/glusterfs/data_scripts.vol on the bricks. Ian |
[Prev in Thread] | Current Thread | [Next in Thread] |